From: Urs Thuermann <urs@isnogud.escape.de>
To: linux-smp@vger.kernel.org
Subject: Dual Core vs. Dual CPU
Date: 23 Apr 2006 20:22:31 +0200 [thread overview]
Message-ID: <m2d5f8qhi0.fsf@janus.isnogud.escape.de> (raw)
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?
urs
next reply other threads:[~2006-04-23 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 18:22 Urs Thuermann [this message]
2006-04-24 0:37 ` Dual Core vs. Dual CPU Robert M. Hyatt
2006-04-24 4:07 ` Bill Davidsen
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=m2d5f8qhi0.fsf@janus.isnogud.escape.de \
--to=urs@isnogud.escape.de \
--cc=linux-smp@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).