[issue1841] vfscache panic when creating many links

[Venkatesh Srinivas (via DragonFly issue tracker)]

Venkatesh Srinivas <me at acm.jhu.edu> added the comment:

Okay - presumably we only want to clean out ncps if there is pressure on the 
zone without vnode pressure. Would tracking the link : vnode ratio and cleaning 
namecache entries before entering the loop based on that ratio be worth doing? 
Currently are there interfaces to ask the namecache to clean itself? 
(vnlrureclaim() seems brutal)...

Currently ncp->name is also allocated from the VFSCACHE zone, along with 
namecache hashes; moving them to private zones would reduce load on the VFSCACHE 
zone, and those zones would be implicitly limited by the vnode limit and 
whatever limiting on ncps is there...

_____________________________________________________
DragonFly issue tracker <bugs at lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1841>
_____________________________________________________