From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
akpm@linux-foundation.org, nickpiggin@yahoo.com.au,
linux-kernel@vger.kernel.org
Subject: Re: [patch] sched: align rq to cacheline boundary
Date: Tue, 10 Apr 2007 09:40:54 -0700 [thread overview]
Message-ID: <20070410164054.GI3948@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070410062421.GA23274@elte.hu>
On Tue, Apr 10, 2007 at 08:24:22AM +0200, Ingo Molnar wrote:
>
> * 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.
>
> > -static DEFINE_PER_CPU(struct rq, runqueues);
> > +static DEFINE_PER_CPU(struct rq, runqueues) ____cacheline_aligned_in_smp;
>
> ouch!! Now how did _that_ slip through. The runqueues had been
> cacheline-aligned for ages. Or at least, they were supposed to be.
perhaps the per_cpu definition gave the impression of cacheline aligned too..
>
> could you see any improvement in profiles or workloads with this patch
> applied? (just curious - it's an obviously right fix)
We have seen 0.5% perf improvement on database workload on a 2 node setup.
0.5% is a very good improvement for this workload.
thanks,
suresh
prev parent reply other threads:[~2007-04-10 16:42 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
2007-04-10 6:24 ` Ingo Molnar
2007-04-10 16:40 ` Siddha, Suresh B [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=20070410164054.GI3948@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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