From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Timothy Miller <miller@techsource.com>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
richard.brunner@amd.com, linux-kernel@vger.kernel.org
Subject: Re: Intel vs AMD64
Date: Thu, 26 Feb 2004 14:45:35 -0500 [thread overview]
Message-ID: <403E4CDF.3030300@coyotegulch.com> (raw)
In-Reply-To: <403E4681.20603@techsource.com>
Timothy Miller wrote:
> In other words, Intel's implementation deviates from the architecture as
> defined by AMD. So it's not 100% compatible. I just want this point to
> be clear.
There may exist non-instruction-set differences between the chips as
well. Opteron systems (which have per-CPU memory control) operate as
NUMA machines; will the same be true for any of Intel's ia32e chips?
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Software Invention for High-Performance Computing
next prev parent reply other threads:[~2004-02-26 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 5:32 Intel vs AMD64 Nakajima, Jun
2004-02-26 13:39 ` Chris Wedgwood
2004-02-26 14:35 ` Richard B. Johnson
2004-02-26 19:25 ` Timothy Miller
2004-02-26 19:46 ` Richard B. Johnson
2004-02-27 18:44 ` H. Peter Anvin
2004-02-26 19:18 ` Timothy Miller
2004-02-26 19:45 ` Scott Robert Ladd [this message]
2004-02-27 14:43 ` Timothy Miller
2004-03-03 17:34 ` Pavel Machek
[not found] <7F740D512C7C1046AB53446D37200173EA28A5@scsmsx402.sc.intel.com.suse.lists.linux.kernel>
[not found] ` <403E4681.20603@techsource.com.suse.lists.linux.kernel>
2004-02-26 20:17 ` Andi Kleen
2004-02-27 14:50 ` Timothy Miller
-- strict thread matches above, loose matches on Subject: below --
2004-02-26 4:28 richard.brunner
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=403E4CDF.3030300@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=richard.brunner@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.