The patch titled fs: inode - remove 8 bytes of padding on 64bits allowing 1 more objects/slab under slub has been removed from the -mm tree. Its filename was fs-inode-remove-8-bytes-of-padding-on-64bits-allowing-1-more-objects-slab-under-slub.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: fs: inode - remove 8 bytes of padding on 64bits allowing 1 more objects/slab under slub From: Richard Kennedy <richard@xxxxxxxxxxxxxxx> This removes 8 bytes of padding from struct inode on 64bit builds, and so allows 1 more object/slab in the inode_cache when using slub. Signed-off-by: Richard Kennedy <richard@xxxxxxxxxxxxxxx> Acked-by: Jan Kara <jack@xxxxxxx> Cc: Christoph Hellwig <hch@xxxxxx> Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- include/linux/fs.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN include/linux/fs.h~fs-inode-remove-8-bytes-of-padding-on-64bits-allowing-1-more-objects-slab-under-slub include/linux/fs.h --- a/include/linux/fs.h~fs-inode-remove-8-bytes-of-padding-on-64bits-allowing-1-more-objects-slab-under-slub +++ a/include/linux/fs.h @@ -729,6 +729,7 @@ struct inode { uid_t i_uid; gid_t i_gid; dev_t i_rdev; + unsigned int i_blkbits; u64 i_version; loff_t i_size; #ifdef __NEED_I_SIZE_ORDERED @@ -738,7 +739,6 @@ struct inode { struct timespec i_mtime; struct timespec i_ctime; blkcnt_t i_blocks; - unsigned int i_blkbits; unsigned short i_bytes; umode_t i_mode; spinlock_t i_lock; /* i_blocks, i_bytes, maybe i_size */ _ Patches currently in -mm which might be from richard@xxxxxxxxxxxxxxx are origin.patch linux-next.patch fs-buffer_head-remove-kmem_cache-constructor-to-reduce-memory-usage-under-slub.patch cpuidle-menu-remove-8-bytes-of-padding-on-64-bit-builds.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html