mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
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: Fri, 28 Oct 2005 10:09:59 -0600	[thread overview]
Message-ID: <m1ek65bp2g.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20051028154109.M9269@linuxwireless.org> (Alejandro Bonilla's message of "Fri, 28 Oct 2005 11:45:54 -0400")

"Alejandro Bonilla" <abonilla@linuxwireless.org> writes:

> On Fri, 28 Oct 2005 09:29:34 -0600, Eric W. Biederman wrote
>> "Alejandro Bonilla" <abonilla@linuxwireless.org> writes:
>> 
>> >> so there is no way to give me back the "lost" memory. Is it possible
>> >> that another motherboard might help?
>> >
>> > AFAIK, No. AMD and Intel will always do the same thing until we all move to
>> > real IA64.
>> 
>> IA64 inherits this part of the architecture from x86, so no magic 
>> fix. This is a fundamentally a chipset limitation, not an 
>> architectural bug.
>
> Probably, but if they add a function to support this, then is a Fix, else it
> would have been there all the time.

It is an optimization.  Most chipsets have a hole from XXX-4GB where
you can't put memory.  In most configurations the hole is only a couple
of megabytes.  Although with PCI-E I think it is now typically about 512M
because of the memory mapped PCI-E config space.

If you put in more that 4G the memory usually shows up at 4G and keeps going.

With memory hoisting that many recent chipsets implement you can see the
memory that would normally be covered by the mmio hole someplace about
4G, so you don't loose any memory in that situation.

Now that I think about it that explains why memory was missing on the
system with PCI-E the memory mapped PCI-E config space was out there
covering it up.

>> rev-E amd64 cpus from AMD all have memory hoisting support,
>> as do all server chipsets from Intel for the last several years.
>
> Not according to the link I provided since we started the conversation. But
> they have done tweaks to start "supporting" all this memory.

I have been writing BIOS's for the last 5 years, on Intel and on AMD boards.
I know exactly what the situation is for the boards and chipsets I
have been dealing with.  I actually find it mildly surprising that
desktop boards don't handle this yet.

>> To avoid this you just need a good chipset and a good BIOS implementation.
>> Any recent server board should be fine.  Hopefully the desktop boards
>> will catch up soon.
>
> I doubt it, Intel is slowly moving to 64bit so applications and OS can catch
> up in the future to leave 32bit behind. (Probably)

???
What has this to do with 32bit and 64bit.  x86_64 (aka amd64+em64t) is
the 64bit desktop architecture, and that is what I am talking about.

Basically everything is 64bit now, the only question is how well does
the chipset and BIOS support your memory configuration.

Eric



  reply	other threads:[~2005-10-28 16:10 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 [this message]
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=m1ek65bp2g.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --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

Powered by JetHome