From: "Richard B. Johnson" <root@chaos.analogic.com>
To: reg@dwf.com
Cc: linux-kernel@vger.kernel.org, reg@orion.dwf.com, linux@horizon.com
Subject: Re: Intel 875 Motherboard cant use 4GB of Memory.
Date: Wed, 2 Jun 2004 08:17:21 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0406020812440.2552@chaos> (raw)
In-Reply-To: <200406011956.i51JuYkD019999@orion.dwf.com>
On Tue, 1 Jun 2004 reg@dwf.com wrote:
>
> > That could be PCI devices. Some (particularly high-end video cards)
> > take up a lot of address space, which comes straight out of the available
> > 4 GB physical address space.
> >
> > Check /proc/iomem.
> >
>
> OK, that leaves me more confused, and (to me) it still looks like a
> BIOS problem rather than a greedy device. Here is the /proc/iomem
> with some decimal annotations: (as noted, there is 4x1GB of memory installed)
>
Not just Intel motherboards. There is 32 bits of address-space.
This needs to be shared between RAM and the I/O addresses of
PCI/Bus and AGP boards. Unfortunately, the PCI/AGP specification
wastes a lot of address space because something that needs 1 megabyte
of address-space must sit on a 1 megabyte boundary. If this
comes after something that used 128 bytes, there is nearly a megabyte
wasted to get to the next boundary. A megabyte here a megabyte there..
pretty soon you are talking about a lot of wasted address-space.
Solution: A 64 bit machine will have the same problem, you end up
wasting RAM address space if it overlays PCI/Bus space. But, you
probably would never opt for a gazzzilion bytes of RAM anyway?
One gazzzilion = 1844 6744 0737 0955 1615 (2 ^ 64)
Just don't put 4 gigs of RAM in a 4 gig address-space and expect
to use it all. Sell the spare 2 gigs or build another PC with it!
Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-06-02 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 7:32 reg
2004-06-01 19:56 ` reg
2004-06-01 20:10 ` Valdis.Kletnieks
2004-06-02 9:56 ` Jurriaan
2004-06-02 12:17 ` Richard B. Johnson [this message]
2004-06-02 19:52 ` clemens
2004-06-03 1:11 ` Brian Gerst
2004-06-03 2:32 ` reg
2004-06-03 11:46 ` Richard B. Johnson
2004-06-03 3:03 ` clemens
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=Pine.LNX.4.53.0406020812440.2552@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=reg@dwf.com \
--cc=reg@orion.dwf.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 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®