From: Bill Davidsen <davidsen@tmr.com>
To: Urs Thuermann <urs@isnogud.escape.de>
Cc: linux-smp@vger.kernel.org
Subject: Re: Dual Core vs. Dual CPU
Date: Mon, 24 Apr 2006 00:07:38 -0400 [thread overview]
Message-ID: <444C4F0A.3070808@tmr.com> (raw)
In-Reply-To: <m2d5f8qhi0.fsf@janus.isnogud.escape.de>
Urs Thuermann wrote:
>I'd like to know what is the difference between a system with a dual
>core CPU compared to two (single core) CPUs. I know dual core means
>two CPUs on one chip, but is it really two complete CPUs or do they
>share some component which is used by both CPU cores?
>
>For example HT duplicates only those parts of CPU which hold the state
>of the program in execution (i.e. program counter, registers, etc.)
>but they share the execution logic which often leads to performance
>loss.
>
>Is there some performance difference between dual core and two real
>CPUs, too? I assume the dual cores on one chip must share the bus
>interface, but since in a multi CPU system only one CPU can access the
>bus at a time, I think this doesn't make a performance difference,
>right?
>
>Can anybody give some clarifiactions on these issue?
>
The bad part is that the cores share a bus connection, the good part is
that it appears that some IPC can be done on chip.
RELATED: has anyone done a measurements on the 955 chip, which is dual
core and HT? On heavily threaded or parallel tasks I find 20-30% drop in
clock time for HT processors, but I wonder if the CPU runs out of memory
bandwidth. My standard test is a kernel compile.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-04-24 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 18:22 Dual Core vs. Dual CPU Urs Thuermann
2006-04-24 0:37 ` Robert M. Hyatt
2006-04-24 4:07 ` Bill Davidsen [this message]
2006-04-26 19:58 ` Urs Thuermann
2006-04-26 20:47 ` Robert M. Hyatt
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=444C4F0A.3070808@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-smp@vger.kernel.org \
--cc=urs@isnogud.escape.de \
/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