From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vlad Zolotarov Subject: Re: [PATCH RESEND] fs: Move bh_cachep to the __read_mostly section Date: Thu, 07 Jun 2012 11:23:16 +0300 Message-ID: <2326820.48IRXJDP2Q@vlad> References: <2325453.OX7ktP55U1@vlad> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Shai@scalemp.com To: viro@zeniv.linux.org.uk Return-path: In-Reply-To: <2325453.OX7ktP55U1@vlad> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Monday 28 May 2012 14:58:42 Vlad Zolotarov wrote: > From: Shai Fultheim > > bh_cachep is only written to once on initialization, so move it to the > __read_mostly section. > > Signed-off-by: Shai Fultheim > Signed-off-by: Vlad Zolotarov > --- > fs/buffer.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/buffer.c b/fs/buffer.c > index ad5938c..838a9cf 100644 > --- a/fs/buffer.c > +++ b/fs/buffer.c > @@ -3152,7 +3152,7 @@ SYSCALL_DEFINE2(bdflush, int, func, long, data) > /* > * Buffer-head allocation > */ > -static struct kmem_cache *bh_cachep; > +static struct kmem_cache *bh_cachep __read_mostly; > > /* > * Once the number of bh's in the machine exceeds this level, we start Alexander, could u, pls., take a look at this patch? Could u, pls., update me about its state. Should I respin? thanks in advance, vlad