From: belcampo <belcampo@zonnet.nl>
To: Andi Kleen <andi@firstfloor.org>
Cc: Chris Snook <csnook@redhat.com>,
Andrew Buehler <abuehler.kernel@gmail.com>,
Frederik Deweerdt <deweerdt@free.fr>,
linux-kernel@vger.kernel.org
Subject: Re: Hyperthreading performance oddities
Date: Sat, 08 Mar 2008 08:12:10 +0100 [thread overview]
Message-ID: <47D23C4A.1030409@zonnet.nl> (raw)
In-Reply-To: <87zltae3y7.fsf@basil.nowhere.org>
Hi all,
Back to basics:
Kernel 2.6.22.9 smp hyperthreading needs 338.143s
with 2.6.17 kernel smp/hyperthreading needs 247.704s
for exactly the same job on the same machine.
For me it's not about HT vs. non-MT
Henk Schoneveld
next prev parent reply other threads:[~2008-03-08 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 9:36 Hyperthreading performance oddities belcampo
2008-02-22 10:06 ` Frederik Deweerdt
2008-03-07 13:37 ` Andrew Buehler
2008-03-07 19:08 ` Chris Snook
2008-03-07 19:20 ` Andi Kleen
2008-03-08 7:12 ` belcampo [this message]
2008-03-08 7:30 ` Willy Tarreau
2008-03-08 11:46 ` Andi Kleen
2008-03-08 12:34 ` Willy Tarreau
2008-03-08 12:43 ` 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=47D23C4A.1030409@zonnet.nl \
--to=belcampo@zonnet.nl \
--cc=abuehler.kernel@gmail.com \
--cc=andi@firstfloor.org \
--cc=csnook@redhat.com \
--cc=deweerdt@free.fr \
--cc=linux-kernel@vger.kernel.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