From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
mingo@elte.hu, nickpiggin@yahoo.com.au,
linux-kernel@vger.kernel.org,
Ravikiran G Thirumalai <kiran@scalex86.org>
Subject: Re: [patch] sched: align rq to cacheline boundary
Date: Tue, 10 Apr 2007 09:37:00 +0200 [thread overview]
Message-ID: <200704100937.01399.ak@suse.de> (raw)
In-Reply-To: <20070409134057.2d249f0c.akpm@linux-foundation.org>
> >
> > -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,
On x86 just the real possible map now -- that tends to be much smaller.
There might be some other architectures who still allocate per cpu
for all of NR_CPUs (or always set possible map to that), but those
should be just fixed.
> which is
> rather a lot.
We should have solved the problem of limited per cpu space in .22 at least
with some patches by Jeremy. I also plan a few other changes the will
use more per CPU memory again.
> 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.
When he avoids false sharing on remote wakeup it should be more cache friendly.
> Need more convincing, please.
Was this based on some benchmark where it showed?
-Andi
next prev parent reply other threads:[~2007-04-10 7:37 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
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 [this message]
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=200704100937.01399.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--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