Cookie Cache

[ekl@sdf.lonestar.org (Evan K. Langlois)]

====================
interface directly without an intervening library interface.  Adding a
write-through directory cache in the kernel solves the original
problem without introducing new ones.
====================

I think this is a great idea.  Watching the OS traces, I noticed that the
Freadlink call is recursive.  This means that if called on 100 files
it doesn't get called 100 times but 100 * the number of times the path is
nested, so if the directory is 10 directories deep you get 1000 calls.
If there was a cache for all this you would get 110 calls instead.  
Example used in an extreme case, but just adding to Dreaddir or one of
the other calls or making a combined call wouldn't be as effective as
a caching the OS.