Messages in this thread | | | Date | Fri, 1 Oct 2010 02:12:15 -0400 | From | Christoph Hellwig <> | Subject | Re: [PATCH] fs: inode per-cpu last_ino allocator |
| |
Eric,
what workload did this matter for? As mentioned elsewhere we don't actually need to set i_ino in new_inode in many cases. Normal disk/network filesystem already set their own i_ino anyway and don't need it at all. Various in-kernel filesystems don't need any valid i_ino and Nick's full series actually has a patch dealing with it, which only leaves various user-mountable syntetic filesystems that want to generate an inode number, and IMHO they're better off using iunique.
| |