Re: [LSF/MM/BPF TOPIC] Should we make inode->i_ino a u64?
Christoph Hellwig <[email protected]>
| Newsgroups | gmane.linux.ports.m68k,gmane.linux.file-systems,gmane.linux.ports.sh.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Apr 15, 2026 at 11:11:32AM +0200, John Paul Adrian Glaubitz wrote: > So, this went just over Phoronix [1] and as someone who is still invested > in 32-bit architectures, I'm only notified about the performance impact on > these systems now as the pull request has already been sent to Linus. What performance impact do you see? When using modern file systems reducing the memory usage should eventually improve performance, although this change will require additional file system changes to get there. btrfs already has a series out, and I'm working on the XFS conversion to remove the duplicate 64-bit inode information. Either way 7.0 will reduce the inode size already, as the shrinking mutex/rw_semaphore (and for the XFS inode semaphore) cuts a lot of space, which even on 32-bit by far overshadows the increased size of i_ino. I'm also not sure what personal notification you expect? This has been discussion in-and-out on linux-fsdevel.