mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Neakums <sneakums@zork.net>
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 13:12:48 +0000	[thread overview]
Message-ID: <6uvfmbktrj.fsf@zork.zork.net> (raw)
In-Reply-To: <402CC114.8080100@dell633.otpefo.com> (Nagy Tibor's message of "Fri, 13 Feb 2004 13:20:36 +0100")

Nagy Tibor <nagyt@otpbank.hu> writes:

> Hi,
>
> I am sorry, I have found your e-mail address in
> ./arch/i386/kernel/setup.c. I have the problem below since a year, and
> there is no solution yet. I guess, the problem is about e820. The
> problem exists in 2.4.x and also in 2.6.1.
>
> 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.


  reply	other threads:[~2004-02-13 13:13 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 ` Sean Neakums [this message]
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 ` 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=6uvfmbktrj.fsf@zork.zork.net \
    --to=sneakums@zork.net \
    --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

all inboxes | Powered by JetHome®