From: NY Kwok <nykwok@xsmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: amd64 and kernel configuration
Date: Wed, 27 Jul 2005 16:19:42 +1000 [thread overview]
Message-ID: <25f58b7910e09fd5453bb3ec534330d1@xsmail.com> (raw)
In-Reply-To: <pan.2005.07.27.06.10.14.928455@cox.net>
On 27/07/2005, at 4:10 PM, Duncan wrote:
>
> SMP is short for Symmetrical Multi-Processing. Traditionally, it meant
> you had two CPUs. However, hyperthreading is treated by the kernel as
> two
> CPUs, which is why SMP must be enabled to get the hyperthreading
> option.
> Note that the newest thing to come to x86/x86_64 is dual-core CPUs.
> These
> CPUs actually have two logical CPUs in one package. This is better
> than
> hyperthreading because it's the real thing.
Actually, dual-core means they have two physical cores in one package.
Two logical cores = hyperthreading. ;P
On that note, you want the AMD dual cores as well, because they are
much better designed (they have the crossbar architecture all ready to
drop in additional cores, whereas the current Intel dual-core are
really ugly hacks and perform terribly compared to the AMD ones)
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-27 6:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 6:29 [gentoo-amd64] amd64 and kernel configuration Dulmandakh Sukhbaatar
2005-07-27 6:10 ` [gentoo-amd64] " Duncan
2005-07-27 6:19 ` NY Kwok [this message]
2005-07-27 7:50 ` Dulmandakh Sukhbaatar
2005-07-27 7:04 ` Michal Žeravík
2005-07-27 9:58 ` netpython
2005-07-27 12:30 ` Brett Johnson
2005-07-27 15:58 ` [gentoo-amd64] " Duncan
2005-07-27 10:02 ` Duncan
2005-07-27 10:13 ` [gentoo-amd64] " Duncan
2005-07-27 10:27 ` Paolo Ripamonti
2005-07-27 14:19 ` [gentoo-amd64] " Duncan
2005-07-27 14:31 ` Paolo Ripamonti
2005-07-27 16:16 ` [gentoo-amd64] " Duncan
2005-07-27 10:46 ` [gentoo-amd64] " Drew Kirkpatrick
2005-07-27 15:42 ` [gentoo-amd64] " Duncan
2005-07-27 17:07 ` Jean.Borsenberger
2005-07-27 10:18 ` Duncan
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=25f58b7910e09fd5453bb3ec534330d1@xsmail.com \
--to=nykwok@xsmail.com \
--cc=gentoo-amd64@lists.gentoo.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