From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Alejandro Bonilla <abonilla@linuxwireless.org>
Cc: Marcel Holtmann <marcel@holtmann.org>, linux-kernel@vger.kernel.org
Subject: Re: 4GB memory and Intel Dual-Core system
Date: Wed, 2 Nov 2005 11:20:09 -0500 [thread overview]
Message-ID: <20051102162009.GA9488@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20051027211203.M33358@linuxwireless.org>
On Thu, Oct 27, 2005 at 05:15:50PM -0400, Alejandro Bonilla wrote:
> AFAIK, No. AMD and Intel will always do the same thing until we all move to
> real IA64.
Many boards DO allow remapping memory past 3GB to the 4GB+ area to make
it accessable. There should be a BIOS option for remapping memory or
letting software create a memory hole at 3GB. It is NOT normal to not
allow full access to all the memeory on an amd64/em64t system. Of
course the bios defaults are often set so as to provide as much ram to a
32bit OS as possible at the expense of doing it properly for a 64bit OS.
And it looks like the world has no intension of ever moving to IA64, and
that's probably for the best. PowerPC or Alpha or something would make
more sense if you are going to drop x86.
> Unless there is some sort of kernel hack that will do some crazy thing to give
> you the power there.
>
> But hey, look at it this way, if you remove 1GB, you will lose the Dual
> Channel capability.
Len Sorensen
next prev parent reply other threads:[~2005-11-02 16:20 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
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 [this message]
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=20051102162009.GA9488@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=abonilla@linuxwireless.org \
--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®