Re: [RFC 2/3] vfs: get_next_ino(), support for the uniqueness

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

 



Jan Kara:
>   I don't think scanning the whole superblock list is really a viable
> alternative. That is going to contend a lot on inode_sb_list_lock and burn
> a lot of CPU when there is even moderate number of inodes in tmpfs. If we
> ever have to really use unique inode numbers for tmpfs (but I'm not
> convinced - see my other email), we should probably hash those inodes and
> use iunique()...

Actually I tried
static int test_inode_iunique(struct super_block *sb, unsigned long ino)
which is defined fs/inode.c.
But tmpfs doesn't add inode into hash list when creating the inode.


J. R. Okajima
--
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