Re: [RFC][PATCH] ensure i_ino uniqueness in filesystems without permanent inode numbers (via idr)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2006-11-15 at 18:56 +0100, Jörn Engel wrote:
> To keep the hashtable small, as per hch's request.

Adding to the hashtable was my first suggestion (and actually it still
seems reasonable to me), but according to hch, the reason most of these
filesystems don't add their inodes to the hashtable is that they are
generally pinned in memory. Adding them might slow down inode lookups
for filesystems that don't pin their inodes.

Still, even though they're pinned, we need to keep track of them somehow
to know that i_ino is unique. idr is one way, but there are certainly
others. Another approach would be to add a entirely separate hashtable
for these inodes, but I figured I'd try this way first.

-- Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux