From: Mark Zealey <mark@zealos.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: i686 SMP systems with more then 12 GB ram with 2.4.x kernel ?
Date: Thu, 3 Jan 2002 00:17:07 +0000 [thread overview]
Message-ID: <20020103001707.GA11746@itsolve.co.uk> (raw)
In-Reply-To: <1009649897.12942.2.camel@hh2.hhhome.at> <1009992652.1249.11.camel@wookie-laptop.pdx.osdl.net> <1009994687.12942.14.camel@hh2.hhhome.at> <1009995669.1253.17.camel@wookie-laptop.pdx.osdl.net> <1010015450.15492.19.camel@hh2.hhhome.at>
In-Reply-To: <1010015450.15492.19.camel@hh2.hhhome.at>
On Thu, Jan 03, 2002 at 12:50:50AM +0100, Harald Holzer wrote:
> Today i checked some memory configurations and noticed that the low
> memory decreases, when i add more memory to the system,
> and the size of reserved memory increases:
>
> at 1GB ram, are 16,936kB low mem reserved.
> 4GB ram, 72,824kB reserved
> 8GB ram, 142,332kB reserved
> 16GB ram, 269,424kB reserved
> 32GB ram, 532,080kB reserved, usable low mem: 352 MB
> 64GB ram ??
>
> Which function does the reserved memory fulfill ?
> Is it all for paging ?
Yeah, page tables mostly, they have to be kept in low-mem. It's making struct
page's for every single page in that system, and must be kept in the kernel
memory...
I'd doubt if you could get the system to boot at 64 gigs
--
Mark Zealey
mark@zealos.org
mark@itsolve.co.uk
UL++++>$ G!>(GCM/GCS/GS/GM) dpu? s:-@ a16! C++++>$ P++++>+++++$ L+++>+++++$
!E---? W+++>$ N- !o? !w--- O? !M? !V? !PS !PE--@ PGP+? r++ !t---?@ !X---?
!R- b+ !tv b+ DI+ D+? G+++ e>+++++ !h++* r!-- y--
(www.geekcode.com)
next prev parent reply other threads:[~2002-01-03 0:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 18:18 i686 SMP systems with more then 12 GB ram with 2.4.x kernel ? Harald Holzer
2001-12-29 18:45 ` Alan Cox
2001-12-29 21:24 ` M. Edward (Ed) Borasky
2001-12-30 0:25 ` M. Edward (Ed) Borasky
2001-12-30 2:14 ` Harald Holzer
2001-12-30 2:33 ` M. Edward Borasky
2002-01-01 18:15 ` M. Edward Borasky
2002-01-01 18:46 ` Alan Cox
2002-01-01 19:02 ` M. Edward Borasky
2002-01-02 1:16 ` H. Peter Anvin
2002-01-02 21:17 ` Gerrit Huizenga
2002-01-06 8:20 ` Benjamin LaHaise
2002-01-06 16:16 ` Alan Cox
2002-01-06 20:23 ` Benjamin LaHaise
2002-01-06 23:37 ` Chris Wedgwood
2002-01-07 0:29 ` The COUGAR Project M. Edward Borasky
2002-01-07 2:18 ` i686 SMP systems with more then 12 GB ram with 2.4.x kernel ? Marvin Justice
2002-01-07 2:38 ` Chris Wedgwood
2002-01-07 4:40 ` T. A.
2002-01-07 16:20 ` Hugh Dickins
2002-01-02 17:30 ` Timothy D. Witham
[not found] ` <1009994687.12942.14.camel@hh2.hhhome.at>
[not found] ` <1009995669.1253.17.camel@wookie-laptop.pdx.osdl.net>
2002-01-02 23:50 ` Harald Holzer
2002-01-03 0:16 ` Alan Cox
2002-01-03 13:30 ` Rik van Riel
2002-01-04 12:09 ` Hugh Dickins
2002-01-04 12:15 ` Rik van Riel
2002-01-03 0:17 ` Mark Zealey [this message]
2002-01-03 13:28 ` Rik van Riel
2002-01-03 14:33 ` Stephan von Krawczynski
2002-01-03 16:38 ` Rik van Riel
2002-01-03 15:15 ` Anton Blanchard
-- strict thread matches above, loose matches on Subject: below --
2001-12-29 19:25 Dieter Nützel
2002-01-06 18:39 Daniel Freedman
2002-01-06 18:59 ` Marvin Justice
2002-01-06 19:45 ` Daniel Freedman
2002-01-06 20:15 ` Marvin Justice
2002-01-07 5:17 ` Daniel Freedman
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=20020103001707.GA11746@itsolve.co.uk \
--to=mark@zealos.org \
--cc=linux-kernel@vger.kernel.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