From: Anton Blanchard <anton@samba.org>
To: Andi Kleen <ak@muc.de>
Cc: nickpiggin@yahoo.com.au, akpm@osdl.org, linux-arch@vger.kernel.org
Subject: Re: domain setup in 2.6.9rc1-bk6
Date: Tue, 31 Aug 2004 20:09:24 +1000 [thread overview]
Message-ID: <20040831100924.GI26072@krispykreme> (raw)
In-Reply-To: <m3llfvk4vh.fsf@averell.firstfloor.org>
> 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.
Anton
next prev parent reply other threads:[~2004-08-31 10:13 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 [this message]
2004-08-31 11:33 ` Andi Kleen
2004-09-01 0:16 ` Nick Piggin
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=20040831100924.GI26072@krispykreme \
--to=anton@samba.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--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