From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Ben Collins <bcollins@ubuntu.com>,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH 1/4] [x86] Add command line option to enable/disable hyper-threading.
Date: Thu, 30 Nov 2006 10:08:39 -0800 [thread overview]
Message-ID: <20061130100839.A30285@unix-os.sc.intel.com> (raw)
In-Reply-To: <20061130110611.03aff95c@localhost.localdomain>; from alan@lxorguk.ukuu.org.uk on Thu, Nov 30, 2006 at 11:06:11AM +0000
On Thu, Nov 30, 2006 at 11:06:11AM +0000, Alan wrote:
> On Wed, 29 Nov 2006 23:26:05 -0500
> Ben Collins <bcollins@ubuntu.com> wrote:
>
> > This patch adds a config option to allow disabling hyper-threading by
> > default, and a kernel command line option to changes this default at
> > boot time.
> >
> > Signed-off-by: Ben Collins <bcollins@ubuntu.com>
>
> The description is wrong - this does not disable hyperthreading it merely
> leaves one thread idle.
How does this patch achieve that? All this patch does is not detecting the
sibling topology. Kernel will still use all the threads and it just
forgoes the intelligence of which cpus are thread and core siblings and
thus disables the optimizations done by scheduler and doesn't export the
cpu topology to the user through sysfs and /proc.
Am I missing the point of this patch?
thanks,
suresh
> I don't believe Intel have ever published a
> procedure for truely disabling HT, but if you idle a thread you may want
> to adjust the cache settings on a PIV (10.5.6 in the intel docs) and set
> it to shared mode. Need to play more with what the bios does I guess.
>
> So Ack but with the proviso it should say "Ignoring" or "Not using" not
> "Disabling", because it does not do the latter and there seem to be
> performance differences as a result
>
> Acked-by: Alan Cox <alan@redhat.com>
next prev parent reply other threads:[~2006-11-30 18:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 4:26 Ubuntu patch sync for 2.6.20 Ben Collins
2006-11-30 4:26 ` Ben Collins
2006-11-30 4:26 ` Ben Collins
2006-11-30 4:26 ` [PATCH 1/4] [x86] Add command line option to enable/disable hyper-threading Ben Collins
2006-11-30 11:06 ` Alan
2006-11-30 18:08 ` Siddha, Suresh B [this message]
2006-12-01 13:29 ` Pavel Machek
2006-12-01 13:41 ` Ben Collins
2006-12-01 14:32 ` Arjan van de Ven
2006-12-01 15:09 ` Ben Collins
2006-12-01 16:10 ` Arjan van de Ven
2006-12-01 16:14 ` Ben Collins
2006-12-01 16:20 ` Linus Torvalds
2006-12-01 16:56 ` Alan
2006-12-01 17:13 ` Mark Rustad
2006-11-30 4:26 ` [PATCH 2/4] [APIC] Allow disabling of UP APIC/IO-APIC by default, with command line option to turn it on Ben Collins
2006-12-01 8:39 ` Ingo Molnar
2006-12-01 20:56 ` Ben Collins
2006-12-02 8:56 ` Ingo Molnar
2006-11-30 4:26 ` [PATCH 3/4] [ATM] Add CPPFLAGS to byteorder.h check Ben Collins
2006-11-30 4:26 ` [PATCH 4/4] [HVCS] Select HVC_CONSOLE if HVCS is enabled Ben Collins
2006-11-30 12:32 ` Roman Zippel
2006-11-30 15:04 ` Ben Collins
-- strict thread matches above, loose matches on Subject: below --
2006-12-07 22:50 [PATCH 1/4] [x86] Add command line option to enable/disable hyper-threading Peter Cordes
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=20061130100839.A30285@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcollins@ubuntu.com \
--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