So it's good that the problem can be fixed, but the fix makes me worry.

First, I assume increasing maxvnodes wastes some resources?  So the new
scheme is more resource hungry than the old?

Second, the default value should be changed, I presume, to make up for
the change.

	-- Lennart

Luke Mewburn wrote:
> On Sat, Jan 03, 2004 at 01:26:38AM +0900, Kouichirou Hiratsuka wrote:
>   | My system has 1G bytes RAM and free memory was about 550M bytes at
>   | the time of second build of the kernel. But it was very slow by hard
>   | disk accesses. It seems to be related with new memory allocation
>   | scheme for the buffer cache.
> 
> What is
> 	sysctl kern.maxvnodes
> on your system?
> 
> If it's < 50000, have you tried
> 	sysctl -w kern.maxvnodes=131072
> (or even 262144 or larger again) ?