All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andi Kleen <ak@suse.de>
Cc: Anton Blanchard <anton@samba.org>, Andi Kleen <ak@muc.de>,
	akpm@osdl.org, linux-arch@vger.kernel.org,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: domain setup in 2.6.9rc1-bk6
Date: Wed, 01 Sep 2004 10:16:16 +1000	[thread overview]
Message-ID: <413514D0.2020308@yahoo.com.au> (raw)
In-Reply-To: <20040831113328.GA11830@wotan.suse.de>

Andi Kleen wrote:
> On Tue, Aug 31, 2004 at 08:09:24PM +1000, Anton Blanchard wrote:
> 
>>>Problem is that I need a architecture specific hook to 
>>>turn off SMT idle for AMD dual core CPUs, which otherwise
>>>look like SMT siblings. I suppose I will do more tunings
>>>in this area in the future anyways, so having it in the 
>>>architecture would be better.
>>
>>From a ppc64 perspective I liked the merging of the domains code.
>>
>>We could have the ability to override generic domain setup per
>>architecture but leave all the default stuff in there.
> 
> 
> Currently all I want is to disable SD_SHARE_POWER when one flag 
> is set. A simple way to do this would be appreciated.
> 

You can define ARCH_HAS_SCHED_TUNE, and define your own
SD_SIBLING_INIT, SD_CPU_INIT, SD_NODE_INIT. Also, you just
need to define a cpu_sibling_map in order to use CONFIG_SCHED_SMT.

> Later overriding would be fine. A simple way to do this would
> be to declare it weak.
> 

Ingo preferred to do it this way. I can't say I blame him because
the setup code is not exactly something trivial that you want
duplicated everywhere (although it is now much improved).

It would be simple enough to just re-export it to the arch code,
however I guess I agree with tackling that when the need arises.

I think it may not be *too* difficult to even come up with a
decent API to handle more arbitrary setups now. Definitely let
me know when you run into a limitation, and I'll be interested in
fixing it.

Thanks
Nick

  reply	other threads:[~2004-09-01  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31  9:56 domain setup in 2.6.9rc1-bk6 Andi Kleen
2004-08-31 10:09 ` Anton Blanchard
2004-08-31 11:33   ` Andi Kleen
2004-09-01  0:16     ` Nick Piggin [this message]
2004-09-01  1:15       ` Andi Kleen

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=413514D0.2020308@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=ak@muc.de \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.