From: Fawad Lateef <fawadlateef@gmail.com>
To: Joel Jaeggli <joelja@darkwing.uoregon.edu>
Cc: Alejandro Bonilla <abonilla@linuxwireless.org>,
Marcel Holtmann <marcel@holtmann.org>,
linux-kernel@vger.kernel.org
Subject: Re: 4GB memory and Intel Dual-Core system
Date: Fri, 28 Oct 2005 12:19:09 +0500 [thread overview]
Message-ID: <1e62d1370510280019o206be344kc2fbf4cc31ccfabd@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510271947360.32301@twin.uoregon.edu>
On 10/28/05, Joel Jaeggli <joelja@darkwing.uoregon.edu> wrote:
> On Fri, 28 Oct 2005, Fawad Lateef wrote:
>
> > Can you tell me the main differences between IA64 and x86_64 (Opteron)
>
> IA64 is itanium - there are a lot of differences but the principle one for
> your perspective is that you don't want to run x86 code on a itanium, it
> has an x86 instruction decoder but you wouldn't want to use it if you
> could avoid it.
>
OK
> > ? because in your one of the previous mail you said IA64 != EM64T and
>
> emt64 getts lumped with amd64 collectivly x86_64. fundamentaly intels
> implementation is compatible with amd's
>
> > its true, but I know is EM64T/AMD64 in 64-bit mode != IA32 but you
> > said that too EM64T is not really 64-bit, its a IA32 .. Can you give
>
> It is ia32 except with 40 bits of real memory and 48 bits of virtual
> memory and 64 bit registers.
>
And a difference of memory architecture is there tooo. x86_64 in
64-bit mode implements flat memory model but IA32 uses
segmentation/paging. As far as Linux Kernel is concern I know kernel
won't implements segmentation in IA32 so it memory management is
almost compatible with x86_64 except registers/real address /virtual
addresses ...
> one article that's use for getting a start on the instruction set is here:
>
> http://arstechnica.com/cpu/03q1/x86-64/x86-64-1.html
>
Thanks, nice link :)
>
> > me some link which just tells the difference between IA64 (Itanium)
> > and AMD64 (Opteron) ?
>
> you're not likely to care about ia64, so I think what your'e really
> interested in is ia32 vs x86_64 and intel vs amd in the context of x86_64
>
Nops, I am not interested in x86_64 context of intel and amd, I rather
wanted a comparison between the intel and amd server processors
architecture (Itanium and Opteron).
Any ways, Thanks
--
Fawad Lateef
next prev parent reply other threads:[~2005-10-28 7:19 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 20:33 Marcel Holtmann
2005-10-27 20:44 ` Roland Dreier
2005-10-27 20:51 ` Marcel Holtmann
2005-10-27 20:54 ` Roland Dreier
2005-10-27 21:00 ` Marcel Holtmann
2005-10-27 21:06 ` Roland Dreier
2005-10-27 21:08 ` Marcel Holtmann
2005-10-27 21:10 ` Alejandro Bonilla
2005-10-27 20:57 ` Alejandro Bonilla
2005-10-27 20:54 ` Alejandro Bonilla
2005-10-27 20:57 ` Marcel Holtmann
2005-10-27 21:02 ` Alejandro Bonilla
2005-10-27 21:07 ` Marcel Holtmann
2005-10-27 21:15 ` Alejandro Bonilla
2005-10-27 21:19 ` Marcel Holtmann
2005-10-27 22:26 ` Joe Bob Spamtest
2005-10-27 22:05 ` Dave Jones
2005-10-27 22:09 ` Vladimir Lazarenko
2005-11-02 16:21 ` Lennart Sorensen
2005-10-27 22:11 ` Marcel Holtmann
2005-10-27 22:12 ` Dave Jones
2005-10-27 22:17 ` Marcel Holtmann
2005-10-27 22:20 ` Alejandro Bonilla
2005-10-28 0:33 ` Bernd Eckenfels
2005-10-30 22:26 ` Alan Cox
2005-10-31 3:39 ` Alejandro Bonilla Beeche
2005-10-31 13:02 ` Alan Cox
2005-10-31 23:03 ` Martin J. Bligh
2005-11-01 5:03 ` thockin
2005-10-27 22:29 ` Joel Jaeggli
2005-10-27 22:13 ` Alejandro Bonilla
2005-10-27 22:18 ` Marcel Holtmann
2005-10-28 2:35 ` Fawad Lateef
2005-10-28 3:09 ` Joel Jaeggli
2005-10-28 7:19 ` Fawad Lateef [this message]
2005-10-28 15:56 ` Joe Bob Spamtest
2005-10-28 15:29 ` Eric W. Biederman
2005-10-28 15:45 ` Alejandro Bonilla
2005-10-28 16:09 ` Eric W. Biederman
2005-10-30 22:24 ` Alan Cox
2005-11-02 16:20 ` Lennart Sorensen
2005-10-27 22:12 ` Andi Kleen
2005-10-27 21:09 ` linux-os (Dick Johnson)
2005-10-27 21:32 ` Bernd Eckenfels
2005-10-28 20:58 Lukas Hejtmanek
2005-10-29 3:32 ` Dave Jones
2005-10-29 11:15 ` Marcel Holtmann
2005-10-30 6:49 ` Dave Jones
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=1e62d1370510280019o206be344kc2fbf4cc31ccfabd@mail.gmail.com \
--to=fawadlateef@gmail.com \
--cc=abonilla@linuxwireless.org \
--cc=joelja@darkwing.uoregon.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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®