:
:In message <[EMAIL PROTECTED]>, Matt Dillon writes:
:
:> Again, keep in mind that the namei cache is strictly throw-away, but
:> entries can often be reconstituted later by the filesystem without I/O
:> due to the VM Page cache (and/or buffer cache depending on
:> vfs.vmiodirenable). So as with the buffer cache and inode cache,
:> the number of entries can be limited without killing performance or
:> scaleability.
:
:Uhm, that is actually not true.
:
:We keep namecache entries around as long as we can use them, and that
:generally means that recreating them is a rather expensive operation,
:involving creation of vnode and very likely a vm object again.
The vnode cache is a different cache. positive namei hits will
reference a vnode, but namei elements can be flushed at any
time without flushing the underlying vnode.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
