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, 09 Apr 2009 12:31:27 +0200 [thread overview]
Message-ID: <87y6ua86f4.fsf@basil.nowhere.org> (raw)
In-Reply-To: <49DDB609.8050405@narancs.net> (Imre Gergely's message of "Thu, 09 Apr 2009 11:47:05 +0300")
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
> One thing I tried was appending iommu=off at boot, which gave me back
That means if you have any devices that cannot addresses > 32bit they
will panic with that setting.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-04-09 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 8:47 Finding lost memory + kernel messages explained Imre Gergely
2009-04-09 10:31 ` Andi Kleen [this message]
[not found] ` <49DDF2FF.9030501@narancs.net>
2009-04-09 18:22 ` Andi Kleen
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=87y6ua86f4.fsf@basil.nowhere.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