From: Vlad Zolotarov <vlad@scalemp.com>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Shai@scalemp.com
Subject: Re: [PATCH RESEND] fs: Move bh_cachep to the __read_mostly section
Date: Thu, 07 Jun 2012 11:23:16 +0300 [thread overview]
Message-ID: <2326820.48IRXJDP2Q@vlad> (raw)
In-Reply-To: <2325453.OX7ktP55U1@vlad>
On Monday 28 May 2012 14:58:42 Vlad Zolotarov wrote:
> From: Shai Fultheim <shai@scalemp.com>
>
> bh_cachep is only written to once on initialization, so move it to the
> __read_mostly section.
>
> Signed-off-by: Shai Fultheim <shai@scalemp.com>
> Signed-off-by: Vlad Zolotarov <vlad@scalemp.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
next prev parent reply other threads:[~2012-06-07 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 11:58 [PATCH RESEND] fs: Move bh_cachep to the __read_mostly section Vlad Zolotarov
2012-06-07 8:23 ` Vlad Zolotarov [this message]
2012-06-08 0:07 ` Andrew Morton
2012-06-10 9:36 ` Vlad Zolotarov
2012-07-01 11:34 ` Vlad Zolotarov
[not found] ` <CAK-9PRBiqtyiQahunPex9FT2dtKA0k0gv9PR+=sNCXVvn5Bn9Q@mail.gmail.com>
2012-07-02 12:13 ` Vlad Zolotarov
2012-07-02 16:00 ` Chinmay V S
2012-07-02 17:21 ` Vlad Zolotarov
2012-07-02 18:24 ` Chinmay V S
2012-07-03 9:05 ` Vlad Zolotarov
2012-07-03 21:23 ` Andrew Morton
2012-07-04 9:08 ` Vlad Zolotarov
2012-07-03 9:08 ` Vlad Zolotarov
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=2326820.48IRXJDP2Q@vlad \
--to=vlad@scalemp.com \
--cc=Shai@scalemp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.