On Thu, 9 Sep 2010 14:00:44 +0200 Johannes Stezenbach <js@xxxxxxxxx> wrote: > On Tue, Sep 07, 2010 at 03:34:29PM +0200, Johannes Stezenbach wrote: > > > > during some simple disk read throughput testing I observed > > caching behaviour that doesn't seem right. The machine > > has 2G of RAM and AMD Athlon 4850e, x86_64 kernel but 32bit > > userspace, Linux 2.6.35.4. It seems that contents of the > > block cache are not evicted to make room for other blocks. > > (Or something like that, I have no real clue about this.) > > > > Since this is a rather artificial test I'm not too worried, > > but it looks strange to me so I thought I better report it. > > C'mon guys, please comment. Is this a bug or not? > Or is my question too silly? > > > Johannes Well I personally have no clue about the block caching, but perhaps that is an heuristic to prevent the cache from fluctuating too much? Some minimum time a block is hold... in a big linear read the cache is useless anyway most of the time, so it could make some sense... You could try accessing random files after filling up the cache and check if those evict the the cache. That should rule out any linear-read-detection heuristic. Cheers, Flo -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
