public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Andi Kleen <andi@firstfloor.org>, Chris Snook <csnook@redhat.com>,
	Andrew Buehler <abuehler.kernel@gmail.com>,
	Frederik Deweerdt <deweerdt@free.fr>,
	belcampo <belcampo@zonnet.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: Hyperthreading performance oddities
Date: Sat, 8 Mar 2008 13:43:32 +0100	[thread overview]
Message-ID: <20080308124332.GF27074@one.firstfloor.org> (raw)
In-Reply-To: <20080308123436.GA24982@1wt.eu>

>On HT, I normally observe lower performance than on UP.

Hmm weird. It might be interesting to investigate in detail
what is going on there.

> model name      : Intel(R) Core(TM)2 Duo CPU     E8200  @ 2.66GHz
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr lahf_lm

Dual core systems generally have it, It leads to better scheduling
on some older OS because in many aspects dual core is nearer HT than
a true dual socket systems. There was no traditional way to express 
"core siblings" in CPUID so they just faked HT again, but added some 
additional ways to detect real dual coreness. AMD does it similar 
(but slightly different). Of course modern kernels don't need such
hacks anymore. 

-Andi

      reply	other threads:[~2008-03-08 12:42 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
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 [this message]

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=20080308124332.GF27074@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=abuehler.kernel@gmail.com \
    --cc=belcampo@zonnet.nl \
    --cc=csnook@redhat.com \
    --cc=deweerdt@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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