From: Matt Domsch <Matt_Domsch@dell.com>
To: Nagy Tibor <nagyt@otpbank.hu>
Cc: xela@slit.de, mochel@osdl.org, bmoyle@mvista.com,
orc@pell.chi.il.us, linux-kernel@vger.kernel.org
Subject: Re: HIGHMEM
Date: Fri, 13 Feb 2004 07:36:47 -0600 [thread overview]
Message-ID: <20040213073647.B24512@lists.us.dell.com> (raw)
In-Reply-To: <402CC114.8080100@dell633.otpefo.com>; from nagyt@otpbank.hu on Fri, Feb 13, 2004 at 01:20:36PM +0100
On Fri, Feb 13, 2004 at 01:20:36PM +0100, Nagy Tibor wrote:
> We have two Dell Poweredge servers, an older one (PowerEdge 6300) and a
> newer one (PowerEdge 6400). Both servers have 4GB RAM, but the Linux
> kernel uses about 500MB less memory in the newer machine.
This is a FAQ on the Linux-PowerEdge mailing list, and is captured here.
http://lists.us.dell.com/fom-serve/cache/68.html
I have 4GB (or more) RAM in my system. How come Linux sees less than
that?
BIOS must reserve some address space below 4GB for PCI devices such as
RAID controllers, SCSI controllers, NICs, etc. RAID controllers in
particular may request and be given 256MB each. This is address space
that would normally be occupied by RAM, but instead is used by PCI
devices.
RAM addresses start at 0 and grow up. PCI device addresses start at
~4GB and grow down. As long as there is no overlap, the OS will see
all available RAM and make use of it. If there is overlap, the PCI
devices win, and that RAM is not made available to the OS.
This is working as designed per PCI, BIOS, and system chipset
specifications.
You may wish to subscribe to the Linux-PowerEdge@dell.com mailing list
at http://lists.us.dell.com/.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2004-02-13 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 12:20 HIGHMEM Nagy Tibor
2004-02-13 13:12 ` HIGHMEM Sean Neakums
2004-02-13 16:05 ` HIGHMEM Martin J. Bligh
2004-02-13 22:09 ` HIGHMEM Matt Domsch
2004-02-13 22:18 ` HIGHMEM Martin J. Bligh
2004-02-13 17:08 ` HIGHMEM david parsons
2004-02-13 13:36 ` Matt Domsch [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-15 14:39 HIGHMEM Nagy Tibor
2003-04-15 15:14 ` HIGHMEM William Lee Irwin III
2003-04-15 16:03 ` HIGHMEM Samuel Flory
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=20040213073647.B24512@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=bmoyle@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=nagyt@otpbank.hu \
--cc=orc@pell.chi.il.us \
--cc=xela@slit.de \
/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