All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Zhao Forrest <forrest.zhao@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	discuss@x86-64.org, linux-kernel@vger.kernel.org,
	yhlu.kernel@gmail.com, mingo@elte.hu, ak@suse.de
Subject: Re: Does Linux have plan to support memory hole remapping?
Date: Wed, 9 Apr 2008 11:13:07 +0200	[thread overview]
Message-ID: <20080409091307.GG19010@one.firstfloor.org> (raw)
In-Reply-To: <ac8af0be0804090204t79beaca2qe077a28fc4a515ad@mail.gmail.com>

On Wed, Apr 09, 2008 at 05:04:24PM +0800, Zhao Forrest wrote:
> On 4/9/08, Andi Kleen <andi@firstfloor.org> wrote:
> > "Zhao Forrest" <forrest.zhao@gmail.com> writes:
> > >
> > > As we can see from above information that the physical memory in system
> > > is 32768MB(32GB). However OS is only using about
> > > (32768-512)MB(MemTotal:     33010240 kB). Does this mean that this
> > > linux kernel can't use the physical memory remapped
> > > from (4G-512M, 4G) to (32G, 32G+512M)?
> >
> > The linux kernel can only use the memory passed to it by the BIOS.
> > Sometimes they need special BIOS setup options to enable remapping. If
> > there are no such options and you can't upgrade it you're out of luck
> 
> Yes, I have enabled mem hole remapping in BIOS SETUP.
> After looking into dmesg, I found that all 32GB physical memory has
> been allocated to 8 nodes, but why MemTotal shows a less amount of
> memory than 32GB? Interesting......

There is some loss of memory before MemTotal, both from the BIOS
(SMM, Frame Buffer for integrated graphics etc.) and from the kernel
(mem_map which costs a few percent and some other data structures
which are allocated early) 

I covered this in detail in http://halobates.de/memorywaste.pdf

> Does MemTotal means the amount of physical memory allocated to all
> nodes? Or it has different meanings?

Amount of memory left over after early boot on all nodes and visible
to the kernel (so e.g. minus reservations for kdump kernels) 

-Andi

  reply	other threads:[~2008-04-09  9:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  7:54 Does Linux have plan to support memory hole remapping? Zhao Forrest
2008-04-09  8:01 ` Andi Kleen
2008-04-09  8:37   ` Matti Aarnio
2008-04-09  8:49     ` Andi Kleen
2008-04-09  8:54     ` Ingo Molnar
2008-04-09  9:03       ` Andi Kleen
2008-04-10  0:34       ` Kasper Sandberg
2008-04-10  2:09         ` H. Peter Anvin
2008-04-10 12:41           ` Kasper Sandberg
2008-04-10  6:51         ` Andi Kleen
2008-04-09  9:04   ` Zhao Forrest
2008-04-09  9:13     ` Andi Kleen [this message]
2008-04-10  6:51       ` Zhao Forrest
2008-04-10  7:22         ` Andi Kleen
2008-04-09  9:50   ` Arne Georg Gleditsch
2008-04-09 10:03     ` Andi Kleen
2008-04-09 10:16       ` Arne Georg Gleditsch
2008-04-09 18:02       ` Yinghai Lu
2008-04-09 13:34     ` Lennart Sorensen

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=20080409091307.GG19010@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=forrest.zhao@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yhlu.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.