diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2012-06-03 14:50:19 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-06-03 14:50:19 -0700 |
commit | 2f9d3df8aa1cc3c6db5cfa0bad3f0745e04cc27d (patch) | |
tree | f5cb17f1db0e8308eae0c7271c1d2dc86851c95d /include/linux/nfs_idmap.h | |
parent | f8f5701bdaf9134b1f90e5044a82c66324d2073f (diff) | |
download | linux-stable-2f9d3df8aa1cc3c6db5cfa0bad3f0745e04cc27d.tar.gz linux-stable-2f9d3df8aa1cc3c6db5cfa0bad3f0745e04cc27d.tar.bz2 linux-stable-2f9d3df8aa1cc3c6db5cfa0bad3f0745e04cc27d.zip |
vfs: move inode stat information closer together
The comment above it says "Stat data, not accessed from path walking",
but in fact some of inode fields we use for the common stat data was way
down at the end of the inode, causing unnecessary cache misses for the
common stat operations.
The inode structure is pretty big, and this can change padding depending
on field width, but at least on the common 64-bit configurations this
doesn't change the size. Some of our inode layout has historically been
to tro to avoid unnecessary padding fields, but cache locality is at
least as important for layout, if not more.
Noticed by looking at kernel profiles, and noticing that the "i_blkbits"
access stood out like a sore thumb.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/nfs_idmap.h')
0 files changed, 0 insertions, 0 deletions