From: Jan Kara <jack@suse.cz>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: Matthew Wilcox <matthew@wil.cx>,
Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@lst.de>,
lkml <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [PATCH] fs: inode - remove 8 bytes of padding on 64bits allowing 1 more objects/slab under slub
Date: Mon, 15 Feb 2010 12:29:50 +0100 [thread overview]
Message-ID: <20100215112950.GB4194@quack.suse.cz> (raw)
In-Reply-To: <1266232571.2149.10.camel@localhost>
On Mon 15-02-10 11:16:11, Richard Kennedy wrote:
> 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@rsk.demon.co.uk>
Looks good to me.
Acked-by: Jan Kara <jack@suse.cz>
Honza
> ----
> patch against 2.6.33-rc8
> compiled & tested on x86_64 AMDX2
>
> I've been running this patch for over a week with no obvious problems
> regards
> Richard
>
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index b1bcb27..ebb1cd5 100644
> --- a/include/linux/fs.h
> +++ b/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 */
>
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2010-02-15 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 11:16 [PATCH] fs: inode - remove 8 bytes of padding on 64bits allowing 1 more objects/slab under slub Richard Kennedy
2010-02-15 11:29 ` Jan Kara [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100215112950.GB4194@quack.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=richard@rsk.demon.co.uk \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox