Sure -- my bad, I aggregated them all of them up for you: https://github.com/apache/cassandra/search?utf8=✓&q=CLibrary.trySkipCache&type=Code<https://github.com/apache/cassandra/search?utf8=%E2%9C%93&q=CLibrary.trySkipCache&type=Code> https://github.com/apache/cassandra/blob/81f6c784ce967fadb6ed7f58de1328e713eaf53c/test/unit/org/apache/cassandra/utils/CLibraryTest.java#L34 https://github.com/apache/cassandra/blob/81f6c784ce967fadb6ed7f58de1328e713eaf53c/src/java/org/apache/cassandra/db/commitlog/MemoryMappedSegment.java#L102 https://github.com/apache/cassandra/blob/81f6c784ce967fadb6ed7f58de1328e713eaf53c/src/java/org/apache/cassandra/hints/ChecksummedDataInput.java#L218 https://github.com/apache/cassandra/blob/81f6c784ce967fadb6ed7f58de1328e713eaf53c/src/java/org/apache/cassandra/hints/HintsWriter.java#L292 https://github.com/apache/cassandra/blob/81f6c784ce967fadb6ed7f58de1328e713eaf53c/src/java/org/apache/cassandra/io/util/FileHandle.java#L167 https://github.com/apache/cassandra/blob/81f6c784ce967fadb6ed7f58de1328e713eaf53c/src/java/org/apache/cassandra/io/sstable/SSTableRewriter.java#L174 https://github.com/apache/cassandra/blob/f2a354763877cfeaf1dd017b84a7c8ee9eafd885/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java#L2281 https://github.com/apache/cassandra/blob/f2a354763877cfeaf1dd017b84a7c8ee9eafd885/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java#L2282
Or if you use IDEA this should work pretty well too: [cid:543B66BF-5E99-4227-A24D-1AB8C0341D97@localhost] best, kjellman On Oct 18, 2016, at 8:33 AM, Benedict Elliott Smith <bened...@apache.org<mailto:bened...@apache.org>> wrote: ... and continuing in the fashion of behaviours one might like to disabuse people of, no code link is provided. On 18 October 2016 at 16:28, Michael Kjellman <mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com>> wrote: We use posix_fadvise in a bunch of places, and in stereotypical Cassandra fashion no comments were provided. There is a check the OS is Linux (okay, a start) but it turns out the behavior of providing a length of 0 to posix_fadvise changed in some 2.6 kernels. We don't check the kernel version -- or even note it. What is the *expected* outcome of our use of posix_fadvise -- not what does it do or not do today -- but what problem was it added to solve and what's the expected behavior regardless of kernel versions. best, kjellman Sent from my iPhone
