From: Andrew Morton <akpm@linux-foundation.org>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: mingo@elte.hu, nickpiggin@yahoo.com.au,
linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Ravikiran G Thirumalai <kiran@scalex86.org>
Subject: Re: [patch] sched: align rq to cacheline boundary
Date: Mon, 9 Apr 2007 13:40:57 -0700 [thread overview]
Message-ID: <20070409134057.2d249f0c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070409180853.GC3948@linux-os.sc.intel.com>
On Mon, 9 Apr 2007 11:08:53 -0700
"Siddha, Suresh B" <suresh.b.siddha@intel.com> wrote:
> Align the per cpu runqueue to the cacheline boundary. This will minimize the
> number of cachelines touched during remote wakeup.
>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
> ---
>
> diff --git a/kernel/sched.c b/kernel/sched.c
> index b9a6837..eca33c5 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -278,7 +278,7 @@ struct rq {
> struct lock_class_key rq_lock_key;
> };
>
> -static DEFINE_PER_CPU(struct rq, runqueues);
> +static DEFINE_PER_CPU(struct rq, runqueues) ____cacheline_aligned_in_smp;
Remember that this can consume up to (linesize-4 * NR_CPUS) bytes, which is
rather a lot.
Remember also that the linesize on VSMP is 4k.
And that putting a gap in the per-cpu memory like this will reduce its
overall cache-friendliness.
Need more convincing, please.
next prev parent reply other threads:[~2007-04-09 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 18:08 [patch] sched: align rq to cacheline boundary Siddha, Suresh B
2007-04-09 20:40 ` Andrew Morton [this message]
2007-04-09 21:53 ` Ravikiran G Thirumalai
2007-04-09 22:17 ` Siddha, Suresh B
2007-04-10 5:00 ` Ravikiran G Thirumalai
2007-04-10 6:36 ` Ingo Molnar
2007-04-10 23:47 ` Siddha, Suresh B
2007-04-10 7:37 ` Andi Kleen
2007-04-10 6:24 ` Ingo Molnar
2007-04-10 16:40 ` Siddha, Suresh B
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=20070409134057.2d249f0c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=suresh.b.siddha@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox