mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Knoblauch <knobi@knobisoft.de>
To: Gleb Natapov <glebn@voltaire.com>,
	Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to detect multi-core and/or HT-enabled CPUs in 2.4.x and 2.6.x kernels
Date: Wed, 27 Dec 2006 07:41:58 -0800 (PST)	[thread overview]
Message-ID: <20061227154158.54796.qmail@web32608.mail.mud.yahoo.com> (raw)
In-Reply-To: <20061227152240.GC10953@minantech.com>


--- Gleb Natapov <glebn@voltaire.com> wrote:

> On Wed, Dec 27, 2006 at 04:13:00PM +0100, Arjan van de Ven wrote:
> > The original p4 HT to a large degree suffered from a too small
> cache
> > that now was shared. SMT in general isn't per se all that different
> in
> > performance than dual core, at least not on a fundamental level,
> it's
> > all a matter of how many resources each thread has on average. With
> dual
> > core sharing the cache for example, that already is part HT.
> Putting the
> > "boundary" at HT-but-not-dual-core is going to be highly artificial
> and
> > while it may work for the current hardware, in general it's not a
> good
> > way of separating things (just look at the PowerPC processors,
> those are
> > highly SMT as well), and I suspect that your distinction is just
> going
> > to break all the time over the next 10 years ;) Or even today on
> the
> > current "large cache" P4 processors with HT it already breaks.
> (just
> > those tend to be the expensive models so more rare)
> > 
> If I run two threads that are doing only calculations and very little
> or no
> IO at all on the same socket will modern HT and dual core be the same
> (or close) performance wise?
> 
Hi Gleb,
 
 this is a real interesting question. Ganglia is coming [originally]
from the HPC side of computing. At least in the past HT as implemented
on XEONs did help a lot. Running two CPU+memory-bandwith intensive
processes on the same physical CPU would at best result in a 50/50
performance split. So, knowing how many "real" CPUs are in a system is
interesting to us.

 Other workloads (like lots of java threads doing mixed IO and CPU
stuff) of course can benefit from HT.

Cheers
Martin

------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de

  parent reply	other threads:[~2006-12-27 15:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-27 14:16 Martin Knoblauch
2006-12-27 14:24 ` Arjan van de Ven
2006-12-27 14:40   ` Martin Knoblauch
2006-12-27 15:13     ` Arjan van de Ven
2006-12-27 15:22       ` Gleb Natapov
2006-12-27 15:38         ` Arjan van de Ven
2006-12-27 15:41         ` Martin Knoblauch [this message]
2006-12-27 15:53           ` Arjan van de Ven
2006-12-27 15:51         ` Martin Knoblauch
2006-12-27 16:09           ` Arjan van de Ven
2006-12-27 17:14             ` Bernd Eckenfels
2006-12-27 17:52             ` Martin Knoblauch
2006-12-27 19:58               ` Siddha, Suresh B
2006-12-27 14:37 ` Jan Engelhardt

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=20061227154158.54796.qmail@web32608.mail.mud.yahoo.com \
    --to=knobi@knobisoft.de \
    --cc=arjan@infradead.org \
    --cc=glebn@voltaire.com \
    --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

all inboxes | Powered by JetHome®