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, 15 November 2006 10:27:20 -0700, Matthew Wilcox wrote:
> 
> I agree with these problems, but I liked your earlier approach to fixing
> them.  I don't particularly like the idr approach because, as you say,
> it will reuse numbers rapidly.

Is that a problem for nfs only?  Or are there others.  For nfs, Jeff
already increments i_generation, so the (i_ino|i_generation) tupel is
not rapidly reused.

> Why is it these filesystems don't add their inodes to the hashtable?
> Might that not be a more profitable approach to fixing this problem?

To keep the hashtable small, as per hch's request.

Jörn

-- 
/* Keep these two variables together */
int bar;
-
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