lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 07 Jun 2012 11:23:16 +0300 From: Vlad Zolotarov <vlad@...lemp.com> To: viro@...iv.linux.org.uk Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, Shai@...lemp.com Subject: Re: [PATCH RESEND] fs: Move bh_cachep to the __read_mostly section On Monday 28 May 2012 14:58:42 Vlad Zolotarov wrote: > From: Shai Fultheim <shai@...lemp.com> > > bh_cachep is only written to once on initialization, so move it to the > __read_mostly section. > > Signed-off-by: Shai Fultheim <shai@...lemp.com> > Signed-off-by: Vlad Zolotarov <vlad@...lemp.com> > --- > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists