What makes the kernel flush cach entries? If I do a "find ./" the
kernel swallows up about 15000 size-128 and 15000 size-32s... I'de
prefer this memory go to something useful (like buffercache).. How
difficult would it be to impliment a userspace daemon to do watch
for spikes then flush unhit entries?
A more fruitful endeavor would be to go back to one of the 2.1.x
kernels which had Thomas Schoebel's original dcache/inode rewrite code
in it. Take a look at the multi-level aging scheme he employed for
the inodes in that code, that would effectively give the behavior you
are after.