From: Bill Davidsen <davidsen@tmr.com>
To: Johannes Stezenbach <js@linuxtv.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.12-rc6
Date: Fri, 17 Jun 2005 13:48:25 -0400 [thread overview]
Message-ID: <42B30CE9.4050707@tmr.com> (raw)
In-Reply-To: <20050608113718.GA5949@linuxtv.org>
Johannes Stezenbach wrote:
> Brice Goglin wrote:
>
>>Johannes Stezenbach a écrit :
>>
>>>Johannes Stezenbach wrote:
>>>
>>>
>>>>Hype-threading stopped working for me (probably due to
>>>>me not enabling ACPI). dmesg output and .config attached.
>>>>-rc5 worked fine. The board is an Asus P4P800-Deluxe.
>>>>
>>>>dmesg: WARNING: 1 siblings found for CPU0, should be 2
>>>
>>>
>>>Indeed SMT works fine if I enable ACPI.
>>>Is SMT without ACPI not supported?
>>
>>You can pass acpi=ht into the kernel command line to disable
>>ACPI except the minimum required to get HT support.
>
>
> That's nice, but I was thinking along the lines of:
>
> diff -ur linux-2.6.12-rc6.orig/arch/i386/Kconfig linux-2.6.12-rc6/arch/i386/Kconfig
> --- linux-2.6.12-rc6.orig/arch/i386/Kconfig 2005-06-06 23:16:27.000000000 +0200
> +++ linux-2.6.12-rc6/arch/i386/Kconfig 2005-06-08 13:35:08.000000000 +0200
> @@ -503,7 +503,7 @@
>
> config SCHED_SMT
> bool "SMT (Hyperthreading) scheduler support"
> - depends on SMP
> + depends on SMP && ACPI
> default off
> help
> SMT scheduler support improves the CPU scheduler's decision making
>
> Comments? Is this intended?
I would think that you can't do HT without ACPI, so there's no point in
building in HT scheduling unless you can have HT.
Is that what you were asking? I was hoping someone else would comment.
Scheduling is getting harder and harder to get right... I have this
thought of a Beowolf cluster of NUMA machines, with each node being HT
multicore SMP. By "right" I meant "optimal," I'm sure that setup would
do something reasonable with current scheduling.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-06-17 17:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 18:08 Linux v2.6.12-rc6 Linus Torvalds
2005-06-06 19:26 ` Pavel Machek
2005-06-06 19:54 ` Jeff Garzik
2005-06-06 20:05 ` Pavel Machek
2005-06-06 21:11 ` Linus Torvalds
2005-06-06 21:54 ` Bill Davidsen
2005-06-06 20:12 ` Linus Torvalds
2005-06-06 20:14 ` Pavel Machek
2005-06-06 21:13 ` Linus Torvalds
2005-06-06 21:18 ` Pavel Machek
2005-06-06 21:36 ` Linus Torvalds
2005-06-06 21:41 ` Pavel Machek
2005-06-06 21:53 ` Linus Torvalds
2005-06-06 21:57 ` Jesper Juhl
2005-06-06 22:07 ` Russell King
2005-06-07 9:11 ` Johannes Stezenbach
2005-06-08 11:15 ` Johannes Stezenbach
2005-06-08 11:23 ` Brice Goglin
2005-06-08 11:37 ` Johannes Stezenbach
2005-06-17 17:48 ` Bill Davidsen [this message]
2005-06-18 13:57 ` Johannes Stezenbach
2005-06-18 17:10 ` Johannes Stezenbach
2005-06-07 13:05 ` Erik Mouw
2005-06-07 15:28 ` Linus Torvalds
2005-06-07 17:11 ` Erik Mouw
2005-06-07 17:28 ` Linus Torvalds
2005-06-08 2:08 ` Paul Mackerras
2005-06-08 17:11 ` Linus Torvalds
2005-06-08 16:20 ` Nicolas Pitre
2005-06-07 18:47 ` Jean Delvare
2005-06-09 8:10 ` Greg KH
2005-06-09 15:52 ` Jean Delvare
2005-06-09 16:32 ` Greg KH
2005-06-08 13:37 ` segfaults suddenly appearing Jakob Oestergaard
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 6:11 Linux v2.6.12-rc6 Voluspa
2005-06-07 6:18 ` Ingo Molnar
2005-06-07 6:37 ` Voluspa
2005-06-07 7:06 ` Grant Coady
2005-06-07 7:44 ` Dave Airlie
2005-06-07 8:45 ` Voluspa
2005-06-07 8:19 ` Matthias Andree
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=42B30CE9.4050707@tmr.com \
--to=davidsen@tmr.com \
--cc=js@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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