On Mon, Sep 03, 2001 at 01:36:47PM -0400, Thor Lancelot Simon wrote:

 > Another observation: when you have to recycle a vnode, you get one that's
 > basically chosen at random with regard to the current head position.  This
 > is REALLY BAD.  To fix it, we'd need to index the vnode cache some other
 > way than as a hash table, but the fix might give a really large performance
 > increase in some cases.

Well, you can link a vnode into multiple tables, of course... the normal
hash table plus a "inode position" table, or whatever.

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>