From: Josh Fryman <fryman@cc.gatech.edu>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: pavel@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: 2.4.14-pre6
Date: Mon, 5 Nov 2001 16:27:53 -0500 [thread overview]
Message-ID: <20011105162753.626cbdb6.fryman@cc.gatech.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0111051241410.3682-100000@penguin.transmeta.com>
In-Reply-To: <20011102120108.A47@toy.ucw.cz> <Pine.LNX.4.33.0111051241410.3682-100000@penguin.transmeta.com>
> Basically, you get two virtual CPU's per die, and each CPU can run two
> threads at the same time. It slows some stuff down, because it makes for
> much more cache pressure, but Intel claims up to 30% improvement on some
> loads that scale well.
>
> The 30% is probably a marketing number (ie it might be more like 10% on
> more normal loads), but you have to give them points for interesting
> technology <)
Specifically, the 30% comes in two places. Using Intel proprietary
benchmarks (unreleased, according to the footnotes) they find that a
typical IA32 instruction mix uses some 35% of system resources in an
advanced device like the P4 with NetBurst. the rest is idle.
by using the SMT model with two virtual systems - each with complete
register sets and independent APICs, sharing only the backend exec
units - they claim you get a 30% improvement in wall-clock time. This
is supposed to be on their benchmarks *without* recompiling anything. To
get "additional" improvement, using code to take advantage of the dual
virtual CPUs nature of the chip and recompiling should give some
unquantified gain.
-josh
to help your searching if you want more details, Intel has called this:
Jackson Technology aka Project Foster aka Hyper-Threading Technology
and is known in the rest of the world as SMT.
Intel has a whitepaper or two available for download. If you can't find
them at developer.intel.com or via Google, let me know and I've got some
copies laying around. Amusingly, they seem to be ultra scared of
releasing any real information about it. Alpha was working on a 4-way
design that seemed a bit more clever for the 21464, which appears to be
destined for the bit bucket now :(
next prev parent reply other threads:[~2001-11-05 21:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 8:00 2.4.14-pre6 Linus Torvalds
2001-10-31 9:10 ` 2.4.14-pre6 Andrew Morton
2001-10-31 9:29 ` 2.4.14-pre6 Jens Axboe
2001-10-31 9:30 ` 2.4.14-pre6 bert hubert
2001-10-31 19:27 ` 2.4.14-pre6 Michael Peddemors
2001-10-31 19:38 ` 2.4.14-pre6 Linus Torvalds
2001-10-31 19:55 ` 2.4.14-pre6 Mike Castle
2001-10-31 20:02 ` 2.4.14-pre6 Rik van Riel
2001-10-31 23:18 ` 2.4.14-pre6 Erik Andersen
2001-10-31 23:40 ` 2.4.14-pre6 Dax Kelson
2001-10-31 23:57 ` 2.4.14-pre6 Michael Peddemors
2001-10-31 19:52 ` 2.4.14-pre6 Philipp Matthias Hahn
2001-10-31 21:05 ` 2.4.14-pre6 H. Peter Anvin
2001-11-01 19:14 ` 2.4.14-pre6 Pozsar Balazs
2001-11-02 12:01 ` 2.4.14-pre6 Pavel Machek
2001-11-05 20:43 ` 2.4.14-pre6 Charles Cazabon
2001-11-05 20:49 ` 2.4.14-pre6 Linus Torvalds
2001-11-05 21:04 ` 2.4.14-pre6 Johannes Erdfelt
2001-11-05 21:08 ` 2.4.14-pre6 Wilson
2001-11-05 21:27 ` Josh Fryman [this message]
2001-11-05 19:04 ` 2.4.14-pre6 Gérard Roudier
2001-11-02 16:48 ` 2.4.14-pre6 jogi
2001-11-03 12:47 ` 2.4.14-pre6 Mike Galbraith
2001-11-03 18:01 ` 2.4.14-pre6 Linus Torvalds
2001-11-03 19:07 ` 2.4.14-pre6 Mike Galbraith
2001-10-31 16:15 2.4.14-pre6 Linus Torvalds
2001-10-31 18:36 ` 2.4.14-pre6 Andrew Morton
2001-10-31 19:06 ` 2.4.14-pre6 Linus Torvalds
2001-11-01 10:20 ` 2.4.14-pre6 Neil Brown
2001-11-01 20:55 ` 2.4.14-pre6 Andrew Morton
2001-11-02 8:00 ` 2.4.14-pre6 Helge Hafting
2001-11-04 22:34 ` 2.4.14-pre6 Pavel Machek
2001-11-04 23:16 ` 2.4.14-pre6 Daniel Phillips
2001-11-01 21:28 ` 2.4.14-pre6 Chris Mason
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=20011105162753.626cbdb6.fryman@cc.gatech.edu \
--to=fryman@cc.gatech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®