On Mon, 2008-07-28 at 17:53 +0100, Miguel Sousa Filipe wrote: > Hi all, > > On Mon, Jul 28, 2008 at 4:09 PM, Chris Mason <chris.mason@xxxxxxxxxx> wrote: > > Yan and I are hammering this out a little, I've attached my current > > patches. > > > > I was seeing cache misses after long stress runs, which I think is > > coming from references on the higher levels of the tree making us skip > > some leaves while dropping the transaction that added them. > > > > My new version using a single cache per root, and should avoid these > > misses. > > Just curious, what is the cache size and or eviction policy? > Is it LFU or LRU, fifo, something custom? Would ARC be a good policy > for this purpose? > Since this is a cache of the extents pointers in a COW block, things are only written once, and these items are only read once most of the time. So, we don't need anything fancy, just a direct access list that we can use to pull off really old things. In this case, it is just a list head. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
