From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Pekka J Enberg" <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, sct@redhat.com,
adilger@clusterfs.com, clameter@sgi.com
Subject: Re: [PATCH 1/4] ext2: remove inode constructor
Date: Thu, 10 May 2007 17:06:04 +0530 [thread overview]
Message-ID: <a781481a0705100436r389bad5ct85bd2a1bec9ab0d0@mail.gmail.com> (raw)
In-Reply-To: <20070509133948.814128f4.akpm@linux-foundation.org>
On 5/10/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Sat, 5 May 2007 12:57:46 +0300 (EEST)
> Pekka J Enberg <penberg@cs.helsinki.fi> wrote:
>
> > From: Pekka Enberg <penberg@cs.helsinki.fi>
> >
> > As alloc_inode() touches the same cache line as init_once(), we gain
> > nothing from using slab constructors.
> >
> > Cc: Stephen C. Tweedie <sct@redhat.com>
> > Cc: Andreas Dilger <adilger@clusterfs.com>
> > Cc: Christoph Lameter <clameter@sgi.com>
> > Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
> > ---
> > fs/ext2/super.c | 32 +++++++++++++-------------------
> > 1 file changed, 13 insertions(+), 19 deletions(-)
> >
> > Index: 26-mm/fs/ext2/super.c
> > ===================================================================
> > --- 26-mm.orig/fs/ext2/super.c 2007-05-05 12:26:15.000000000 +0300
> > +++ 26-mm/fs/ext2/super.c 2007-05-05 12:30:50.000000000 +0300
> > @@ -140,16 +140,24 @@ static struct kmem_cache * ext2_inode_ca
> > static struct inode *ext2_alloc_inode(struct super_block *sb)
> > {
> > struct ext2_inode_info *ei;
> > - ei = (struct ext2_inode_info *)kmem_cache_alloc(ext2_inode_cachep,
> > - GFP_KERNEL|__GFP_RECLAIMABLE);
> > + struct inode *inode;
> > +
> > + ei = kmem_cache_alloc(ext2_inode_cachep, GFP_KERNEL|__GFP_RECLAIMABLE);
> > if (!ei)
> > return NULL;
> > + rwlock_init(&ei->i_meta_lock);
> > +#ifdef CONFIG_EXT2_FS_XATTR
> > + init_rwsem(&ei->xattr_sem);
> > +#endif
> > + mutex_init(&ei->truncate_mutex);
>
> ext2 has no truncate_mutex.
2.6.21-mm2/broken-out/ext2-reservations.patch seems to have added one.
> These patches are rather tangled up with the unmerged __GFP_RECLAIMABLE
> stuff.
So _and_ the unmerged ext2-reservations stuff, you mean :-)
> I'll duck them for now.
next prev parent reply other threads:[~2007-05-10 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 9:57 Pekka J Enberg
2007-05-09 20:39 ` Andrew Morton
2007-05-10 11:36 ` Satyam Sharma [this message]
2007-05-10 12:56 ` Pekka Enberg
2007-05-10 18:46 ` Christoph Lameter
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=a781481a0705100436r389bad5ct85bd2a1bec9ab0d0@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=sct@redhat.com \
/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
all inboxes | Powered by JetHome®