making an in-memory hashing table ["name" -> ino_t] with thousands of entries

[Luke Kenneth Casson Leighton <lkcl@lkcl.net>]

dear kernel hackers,

i seek advice on how to do an in-kernel lookup table capable of storing
thousands, potentially hundreds of thousands, of entries.

the reason for this is to move the fuse userspace inode lookup
tables into the kernel.

fuse userspace servers have their own in-memory database of
unique inode numbers which represent the file names, and there is a
communication mechanism between userspace and kernelspace that transfers
those inode numbers, amongst other things.

is there any _sane_ way to do this or should i leave the inode lookup
table where it presently is - in userspace?

bearing in mind that for every file accessed via a fuse
filesystem, a cache entry is created, and therefore the number
of entries could potentially run into hundreds of thousands
of entries.

l.

-- 
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love.  If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />