On Thu, Apr 12, 2001 at 02:24:36PM -0700, a little birdie told me
that Matt Dillon remarked
>
> Without vmiodirenable turned on, any directory exceeding
> vfs.maxmallocbufspace becomes extremely expensive to work with
> O(N * diskIO). With vmiodirenable turned on huge directories
> are O(N), but have a better chance of being in the VM page cache
> so cost proportionally less even though they don't do any
> better on a relative scale.
Speaking of vmiodirenable, what are the issues with it that it's not
enabled by default? ISTR that it's been in a while, and most people
pointed at it have reported success with it, and it seems to have solved
problems here and there for a number of people. What's keeping it from
the general case?
--
Matthew Fuller (MF4839) | [EMAIL PROTECTED]
Unix Systems Administrator | [EMAIL PROTECTED]
Specializing in FreeBSD | http://www.over-yonder.net/
"The only reason I'm burning my candle at both ends, is because I
haven't figured out how to light the middle yet"
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
