From: Andi Kleen <ak@muc.de>
To: nickpiggin@yahoo.com.au, akpm@osdl.org, linux-arch@vger.kernel.org
Subject: domain setup in 2.6.9rc1-bk6
Date: Tue, 31 Aug 2004 11:56:34 +0200 [thread overview]
Message-ID: <m3llfvk4vh.fsf@averell.firstfloor.org> (raw)
Someone deleted arch/x86_64/kernel/domain.c in current BK
and moved the SMT domain setup to generic code.
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.
It seems a bit counterintuitive that we have such a configurable
scheduler, and then there is only a "one size fits all" way
to configure it.
Can part of this code please be moved back to the architecture?
Thanks,
-Andi
next reply other threads:[~2004-08-31 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 9:56 Andi Kleen [this message]
2004-08-31 10:09 ` domain setup in 2.6.9rc1-bk6 Anton Blanchard
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=m3llfvk4vh.fsf@averell.firstfloor.org \
--to=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