From: Michael Neuling <mikey@neuling.org>
To: Diwakar Tundlam <dtundlam@nvidia.com>
Cc: "'Peter Zijlstra'" <a.p.zijlstra@chello.nl>,
"'Ingo Molnar'" <mingo@kernel.org>,
"'Andrew Morton'" <akpm@linux-foundation.org>,
"'Christoph Lameter'" <cl@gentwo.org>,
"'Stephen Rothwell'" <sfr@canb.auug.org.au>,
"'Benjamin Herrenschmidt'" <benh@kernel.crashing.org>,
"'David Rientjes'" <rientjes@google.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>
Subject: Re: [PATCH] sched: Enable arch-specific asym packing option in sched domain
Date: Sat, 05 May 2012 09:20:34 +1000 [thread overview]
Message-ID: <19500.1336173634@neuling.org> (raw)
In-Reply-To: <1DD7BFEDD3147247B1355BEFEFE46652379C3DF103@HQMAIL04.nvidia.com>
> Thanks for clarifying the Power7. I see the point - package vs cpu's within a package.
>
> Yes, this is for Nvidia's ARM Quad-core Tegra CPU. It is a single
> package, organized flatly. To save power, we want cores to be loaded
> up in order from cpu0, 1, etc. The ASYM_PACKING flag seems to do
> exactly what we need if set in the domain flag.
Arrh, so it's not a performance issue but power savings.. that would
this asymmetric packing a lot more appropriate to use.
Mikey
>
> Thanks,
> --Diwakar.
>
> -----Original Message-----
> From: Peter Zijlstra [mailto:a.p.zijlstra@chello.nl]
> Sent: Friday, May 04, 2012 3:30 PM
> To: Diwakar Tundlam
> Cc: 'Ingo Molnar'; 'Andrew Morton'; 'Christoph Lameter'; 'Michael Neuling'; 'Stephen Rothwell'; 'Benjamin Herrenschmidt'; 'David Rientjes'; 'linux-kernel@vger.kernel.org'; Peter De Schrijver
> Subject: RE: [PATCH] sched: Enable arch-specific asym packing option in sched domain
>
> On Fri, 2012-05-04 at 15:18 -0700, Diwakar Tundlam wrote:
> >
> > arch_sd_sibling_asym_packing() is already present under ifdef CONFIG_SMT.
> > I didn't touch that. I only added it to SD_CPU_INIT for all cpu's.
> > I assumed Power7 shouldn't use SD_CPU_INIT.
>
> All archs use SD_CPU_INIT, its the default topology level for a package/socket. So now you've made Power7 prefer lower numbered sockets over higher numbered sockets.. not fatal, but not really nice either.
>
> [ power7 is the only one that implements arch_sd_sibling_asym_packing ]
>
> > Maybe I should define a separate weak symbol, say arch_sd_bias_to_lower_num_cpu()?
> > Then Power7 can define arch_sd_sibling_asym_packing() to be '1' and it
> > will not break all-cpu init.
>
> A slightly saner name would be:
>
> arch_sd_package_asym_packing()
>
> FWIW, I suspect you're wanting to use this for some ARM chip (nvidia doesn't do much else -- aside from this graphics stuff) so that if there's hardly anything it runs on cpu0. Now, last time I checked, these ARM things had only 1 package, so I still don't see the point :-)
>
> I suspect you want to modify SD_MC_INIT() with something like:
>
> arch_sd_mc_asym_packing()
>
> Or is this the big-little thing and you're representing them as separate packages?
>
> See how a little extra information avoids me having to endlessly second guess wtf you're actually wanting to do?
>
next prev parent reply other threads:[~2012-05-04 23:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 20:28 [PATCH] sched: Enable arch-specific asym packing option in sched domain Diwakar Tundlam
2012-05-04 21:17 ` Peter Zijlstra
2012-05-04 22:06 ` Diwakar Tundlam
2012-05-04 22:10 ` Peter Zijlstra
2012-05-04 22:18 ` Diwakar Tundlam
2012-05-04 22:29 ` Peter Zijlstra
2012-05-04 23:18 ` Diwakar Tundlam
2012-05-04 23:20 ` Michael Neuling [this message]
2012-05-04 23:25 ` Diwakar Tundlam
2012-05-04 23:41 ` Michael Neuling
2012-05-07 2:59 ` Michael Wang
2012-05-04 23:55 ` Suresh Siddha
2012-05-05 20:35 ` Peter Zijlstra
2012-05-07 17:25 ` Diwakar Tundlam
2012-05-08 9:46 ` Peter Zijlstra
2012-05-04 22:47 ` Michael Neuling
2012-05-04 22:51 ` Michael Neuling
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=19500.1336173634@neuling.org \
--to=mikey@neuling.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=cl@gentwo.org \
--cc=dtundlam@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pdeschrijver@nvidia.com \
--cc=rientjes@google.com \
--cc=sfr@canb.auug.org.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;
as well as URLs for NNTP newsgroup(s).