From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: "Holzrichter, Bruce" <bruce.holzrichter@monster.com>,
"'Robert Love'" <rml@tech9.net>
Cc: James Bourne <jbourne@MtRoyal.AB.CA>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: RE: Hyperthreading
Date: Wed, 17 Apr 2002 15:48:48 -0700 [thread overview]
Message-ID: <1844830000.1019083728@flay> (raw)
In-Reply-To: <61DB42B180EAB34E9D28346C11535A78177F04@nocmail101.ma.tmpw.net>
> I've seen some Intel bench's and they are specing an increase of 0% to 30%
I think I'd be less cynical about benchmark results that didn't come from the
people trying to sell the product ;-)
> (Though check Anandtech, he did a benchmark on his DB, and got a small
> performance Decrease on a test!)
;-)
Thanks for the pointer.
> After looking at the Hyperthreading Doc's, It looks like they are trying to
> utilize some of the idle time the Execution engine has while waiting for
> other ops to happen, Trace code misses, and such. Strap on an extra
> processor state, and get some extra oomph. Hey, the P4 can use all the
> extra oomph it can get!
It sounds like a good idea in theory, but the fact that they share the TLB
cache and other things makes me rather dubious about whether it's really
worth it. I'm not saying it's necessarily bad, I'm just not convinced it's good
yet. Introducing more processors to the OS has it's own problems to deal
with (ones we're interested in solving anyway).
Real world benchmarks from people other than Intel should make interesting
reading .... I think we need some more smarts in the OS to take real advantage
of this (eg using the NUMA scheduling mods to create cpu pools of 2 "procs"
for each pair, etc) ... will be fun ;-)
M.
next prev parent reply other threads:[~2002-04-17 21:50 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 20:34 Hyperthreading Holzrichter, Bruce
2002-04-17 22:48 ` Martin J. Bligh [this message]
2002-04-18 1:21 ` Hyperthreading James Bourne
-- strict thread matches above, loose matches on Subject: below --
2006-05-29 22:22 Hyperthreading Pete Zaitcev
2006-05-30 7:13 ` Hyperthreading Keir Fraser
2006-05-30 8:18 ` Hyperthreading Christian Limpach
2003-11-25 9:44 hyperthreading Gábor Lénárt
2003-11-25 9:48 ` hyperthreading Emiliano 'AlberT' Gabrielli
2003-11-25 10:05 ` hyperthreading Gábor Lénárt
2003-11-25 10:16 ` hyperthreading Arjan van de Ven
2003-11-25 10:32 ` hyperthreading Måns Rullgård
2003-11-25 10:45 ` hyperthreading Mikael Pettersson
2003-11-29 13:29 ` hyperthreading Bill Davidsen
2003-12-01 10:53 ` hyperthreading Emiliano 'AlberT' Gabrielli
2003-11-25 10:22 ` hyperthreading Karl Pitrich
2002-08-22 12:58 Hyperthreading Nir Soffer
2002-08-22 14:30 ` Hyperthreading Hugh Dickins
2002-08-22 9:15 Hyperthreading Marc Dietrich
2002-08-22 14:06 ` Hyperthreading Hugh Dickins
2002-08-22 14:36 ` Hyperthreading Marc Dietrich
2002-08-21 22:56 Hyperthreading Nakajima, Jun
2002-08-21 23:45 ` Hyperthreading Alan Cox
2002-08-21 11:32 Hyperthreading Reed, Timothy A
2002-08-21 13:48 ` Hyperthreading James Bourne
2002-08-21 17:33 ` Hyperthreading Hugh Dickins
2002-08-21 19:34 ` Hyperthreading James Bourne
2002-08-21 21:16 ` Hyperthreading Kelsey Hudson
2002-08-21 21:55 ` Hyperthreading Banai Zoltan
2002-08-22 8:05 ` Hyperthreading venom
2002-08-26 19:00 ` Hyperthreading Kelsey Hudson
2002-08-22 8:00 ` Hyperthreading venom
2002-08-23 7:28 ` Hyperthreading Gilad Ben-Yossef
2002-08-23 8:10 ` Hyperthreading Hugh Dickins
2002-08-23 8:27 ` Hyperthreading Alan Cox
2002-08-23 8:12 ` Hyperthreading venom
2002-04-18 1:52 Hyperthreading Holzrichter, Bruce
2002-04-17 20:02 SMP P4 APIC/interrupt balancing James Bourne
2002-04-17 21:10 ` Hyperthreading Martin J. Bligh
2002-04-17 20:15 ` Hyperthreading Robert Love
2002-04-17 20:23 ` Hyperthreading Dave Jones
2002-04-17 21:24 ` Hyperthreading Jeff V. Merkey
2002-04-17 20:25 ` Hyperthreading James Bourne
2002-04-17 21:26 ` Hyperthreading Jeff V. Merkey
2002-04-18 0:31 ` Hyperthreading Martin J. Bligh
2002-04-18 4:50 ` Hyperthreading Jeff V. Merkey
2002-04-17 22:12 ` Hyperthreading Alan Cox
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=1844830000.1019083728@flay \
--to=martin.bligh@us.ibm.com \
--cc=bruce.holzrichter@monster.com \
--cc=jbourne@MtRoyal.AB.CA \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
/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.