All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Diwakar Tundlam <dtundlam@nvidia.com>
Cc: "'Ingo Molnar'" <mingo@kernel.org>,
	"'Andrew Morton'" <akpm@linux-foundation.org>,
	"'Christoph Lameter'" <cl@gentwo.org>,
	"'Michael Neuling'" <mikey@neuling.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 00:29:46 +0200	[thread overview]
Message-ID: <1336170586.16236.11.camel@twins> (raw)
In-Reply-To: <1DD7BFEDD3147247B1355BEFEFE46652379C3DF102@HQMAIL04.nvidia.com>

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?

  reply	other threads:[~2012-05-04 22:30 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 [this message]
2012-05-04 23:18         ` Diwakar Tundlam
2012-05-04 23:20           ` Michael Neuling
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=1336170586.16236.11.camel@twins \
    --to=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=mikey@neuling.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 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.