From: Eial Czerwacki <eial@scalemp.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org,
"Shai Fultheim (Shai@ScaleMP.com)" <Shai@scalemp.com>
Subject: Re: [PATCH] Move mostly read variables to __read_mostly section.
Date: Tue, 25 Oct 2011 09:25:16 +0200 [thread overview]
Message-ID: <4EA6645C.2010408@scalemp.com> (raw)
In-Reply-To: <m2sjmj572m.fsf@firstfloor.org>
On 10/24/2011 06:47 AM, Andi Kleen wrote:
> Eial Czerwacki<eial@scalemp.com> writes:
>> * Once the number of bh's in the machine exceeds this level, we start
>> --- a/kernel/time/timekeeping.c 2010-05-12 14:59:32.000000000 -0700
>> +++ b/kernel/time/timekeeping.c 2010-05-24 11:56:32.000000000 -0700
>> @@ -154,7 +154,7 @@ __cacheline_aligned_in_smp DEFINE_SEQLOC
>> * used instead.
>> */
>> static struct timespec xtime __attribute__ ((aligned (16)));
>> -static struct timespec wall_to_monotonic __attribute__ ((aligned (16)));
>> +static struct timespec wall_to_monotonic __attribute__ ((aligned
>> (16))) __read_mostly;
>
> That means that a common time fetch/update call will usually have to fetch two
> cachelines now instead of one, because it needs xtime and
> wall_to_monotonic. Usually those end up nearby.
>
> On the other hand it's rare to fetch wall_to_monotonic without xtime.
>
> So if anything all those variables should be grouped together in a
> single cacheline, but definitely not split like you do.
>
> The other changes in your patch are fine for me.
>
> -Andi
Hello Andi,
Thanks for the input, we've removed the mentioned above section from the
patch and it will be handled in a different patch.
the new patch is as follows:
Signed-off-by: Eial Czerwacki<eial@ScaleMP.com>
Signed-off-by: Shai Fultheim<Shai@ScaleMP.com>
---
--- a/fs/buffer.c 2010-05-12 14:59:32.000000000 -0700
+++ b/fs/buffer.c 2010-05-24 11:56:32.000000000 -0700
@@ -3233,7 +3233,7 @@ SYSCALL_DEFINE2(bdflush, int, func, long
/*
* Buffer-head allocation
*/
-static struct kmem_cache *bh_cachep;
+static struct kmem_cache __read_mostly *bh_cachep;
/*
* Once the number of bh's in the machine exceeds this level, we start
prev parent reply other threads:[~2011-10-25 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 18:23 [PATCH] Move mostly read variables to __read_mostly section Eial Czerwacki
2011-10-24 4:47 ` Andi Kleen
2011-10-25 7:25 ` Eial Czerwacki [this message]
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=4EA6645C.2010408@scalemp.com \
--to=eial@scalemp.com \
--cc=Shai@scalemp.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
/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.