From: Dave Hansen <dave@linux.vnet.ibm.com>
To: paul.szabo@sydney.edu.au
Cc: psz@maths.usyd.edu.au, 695182@bugs.debian.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC] Reproducible OOM with just a few sleeps
Date: Thu, 17 Jan 2013 13:55:24 -0800 [thread overview]
Message-ID: <50F8734C.2080906@linux.vnet.ibm.com> (raw)
In-Reply-To: <201301172104.r0HL4F9k005128@como.maths.usyd.edu.au>
On 01/17/2013 01:04 PM, paul.szabo@sydney.edu.au wrote:
>>> On my large machine, 'free' fails to show about 2GB memory ...
>> You probably have a memory hole. ...
>> The e820 map (during early boot in dmesg) or /proc/iomem will let you
>> locate your memory holes.
>
> Now that my machine is running an amd64 kernel, 'free' shows total Mem
> 65854128 (up from 64447796 with PAE kernel), and I do not see much
> change in /proc/iomem output (below). Is that as should be?
Yeah, that all looks sane. Your increased memory is because your 64GB
machine had some of its memory mapped _above_ the 64GB physical memory
limit that PAE has.
/proc/iomem is generally just a dump of what the hardware *is*, so it
shouldn't change between kernels.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-17 21:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 21:04 [RFC] Reproducible OOM with just a few sleeps paul.szabo
2013-01-17 21:55 ` Dave Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-15 10:25 Sedat Dilek
2013-01-12 19:41 paul.szabo
2013-01-12 3:31 paul.szabo
2013-01-14 15:00 ` Dave Hansen
2013-01-14 20:36 ` paul.szabo
2013-01-15 0:56 ` Dave Hansen
2013-01-15 2:16 ` paul.szabo
2013-01-30 12:51 ` Pavel Machek
2013-01-30 15:32 ` Dave Hansen
2013-01-30 19:40 ` paul.szabo
2013-02-17 9:10 ` Simon Jeons
2013-02-24 22:10 ` paul.szabo
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=50F8734C.2080906@linux.vnet.ibm.com \
--to=dave@linux.vnet.ibm.com \
--cc=695182@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul.szabo@sydney.edu.au \
--cc=psz@maths.usyd.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).