linux-kernel - Re: [PATCH] fs: Move bh_cachep to the __read

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201205031426.27432.vlad@scalemp.com>
Date:	Thu, 3 May 2012 14:26:26 +0300
From:	Vlad Zolotarov <vlad@...lemp.com>
To:	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>
Cc:	"linux-kernel" <linux-kernel@...r.kernel.org>,
	alan@...rguk.ukuu.org.uk,
	"Shai Fultheim (Shai@...leMP.com)" <Shai@...lemp.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] fs: Move bh_cachep to the __read_mostly section

On Tuesday, April 24, 2012 02:22:22 pm 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 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/buffer.c b/fs/buffer.c
> index 36d6665..a1d82fb 100644
> --- a/fs/buffer.c
> +++ b/fs/buffer.c
> @@ -3151,7 +3151,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

Thomas, Ingo, Peter, Alan, do u want me to respin this patch? 
(Alan, this one is not x86 ;))

Could u, pls., advice what should be done for it to be applied?

thanks,
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/