Hi David,
Thank you for your comments. I actually agree with most of the things
you pointed out, so I'll focus my reply here only.
Also, this doesn't address the problem I originally commented on -
it only shrinks the dcache, not the inode or filesystem caches that
hold all the memory.
I understand that the icache is a greater memory user than the dcache.
I also understand that the icache can be dirty due to pending IO.
I am also okay to shrink some of the icache every time we shrink the
dcache - and see below, this might happen if I change they way I am
calling the shrinker.
However, since the dcache precedes the icache in the cache hierarchy,
and is the actual entity pinning the icache into memory, I don't see a
reason to *limit* the icache size, since once the dcache is limited,
anything holding the icache into memory will go away eventually, and the
shrinkers that run during memory pressure will be able to get rid of it.
I mentioned the new per-sb shrinkers for a
reason - you should be calling them, not __shrink_dcache_sb(). i.e.
building a scan_control structure and calling
sb->shrinker.shrink(&sb->shrinker,&sc);
Would you be okay with having prune_super() being called whenever the
nr_dentries_max limit is reached? It will effectively shrink both
the icache and the dcache, using the dentry limit as a trigger only.
I'm seriously starting to think that this needs to share an
implementation with the mm shrinker code, because it already
solves most of these problems...
I have to think more about that. Hold on!
--
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
