leak of the vnodes

[Petr Salinger]

> You can either increase kern.maxvnodes, the default value is very
> conservative on amd64, where a lot of KVA is available. On the other
> hand, increase of the value on i386 could easily cause KVA exhaustion.

The increase helps, the system become responsive. In fact I previously 
suspected scheduler, but change to 4BSD, UP, nopreemption didn't helped.

The build directory of gcc-4.3 is in a separated mount point. Even after 
the build is stopped and the mount point unmounted, the vfs.numvnodes
is still to high. The temporary files (*.s) are in /tmp, but they have 
been deleted, so my expectation is that vfs.numvnodes should lower 
significantly.

> Another possible workaround, if you do not need path resolutions in /proc
> or lsof(1), is to set sysctl vfs.vlru_allow_cache_src=1.

I will test this.

Petr