From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Sean Neakums <sneakums@zork.net>, Nagy Tibor <nagyt@otpbank.hu>,
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 14:18:54 -0800 [thread overview]
Message-ID: <46620000.1076710734@flay> (raw)
In-Reply-To: <20040213160909.A6102@lists.us.dell.com>
> On Fri, Feb 13, 2004 at 08:05:14AM -0800, Martin J. Bligh 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.
>> >
>> > I may be talking through my hat, but I think that in this case you
>> > need to select the option for support of 64G highmem. If I recall,
>> > "4G highmem" refers not to the total amount to the memory, but to the
>> > highest physical address that can be accessed.
>>
>> That's exactly correct. Whether the gain of 500MB of RAM is worth the
>> overhead of PAE is another question ... but that's how to do it ;-)
>
> If the chipset and BIOS can't remap the physical RAM out of the
> address space needed by the PCI devices and into PAE space, then PAE
> doesn't buy you anything. You need chipset support for RAM remapping,
> which doesn't exist on the servers mentioned.
Ah, didn't realise you had a hardware problem as well ;-)
M.
next prev parent reply other threads:[~2004-02-13 22:21 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 ` Martin J. Bligh [this message]
2004-02-13 17:08 ` HIGHMEM david parsons
2004-02-13 13:36 ` HIGHMEM Matt Domsch
-- 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=46620000.1076710734@flay \
--to=mbligh@aracnet.com \
--cc=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=sneakums@zork.net \
--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