mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Imre Gergely <gimre@narancs.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Finding lost memory + kernel messages explained
Date: Thu, 9 Apr 2009 20:22:04 +0200	[thread overview]
Message-ID: <20090409182204.GN14687@one.firstfloor.org> (raw)
In-Reply-To: <49DDF2FF.9030501@narancs.net>

cc to mailing list restored. please don't drop this.

On Thu, Apr 09, 2009 at 04:07:11PM +0300, Imre Gergely wrote:
> Andi Kleen wrote:
> >Imre Gergely <gimre@narancs.net> writes:
> >>That would be around 3896MB. My question is: where does the memory go?
> >>Is it normal to 'lose' that much (~130MB) ?
> >
> >I wrote a paper about this topic some time ago.
> >
> >http://halobates.de/memory.pdf
> >http://halobates.de/memorywaste.pdf
> 
> I tried to understand what you wrote there a bit, but it's still pretty 
> confusing ;)

Modern hardware is complicated.

> [    0.004000] Memory: 3980848k/5177344k available (3115k kernel code, 
> 147212k reserved, 1573k data, 540k init)
> 
> There seems to be 5GB of memory, I don't understand where this is coming 
> from. There is a gap in the mapping 

PCs have memory holes below 1MB and below 4GB. The 4GB hole can be
rather large because it contains IO mappings for all devices.

(lines 16 and 17 in dmesg output on 
> the pastebin), but why? And what's that 147212k reserved?

The paper explains all this.

-Andi

-- 
ak@linux.intel.com -- Speaking for m1yself only.

  parent reply	other threads:[~2009-04-09 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  8:47 Imre Gergely
2009-04-09 10:31 ` Andi Kleen
     [not found]   ` <49DDF2FF.9030501@narancs.net>
2009-04-09 18:22     ` Andi Kleen [this message]
2009-04-10  0:57 ` Robert Hancock

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=20090409182204.GN14687@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=gimre@narancs.net \
    --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

Powered by JetHome