From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jiang Liu <liuj97@gmail.com>,
sworddragon2@aol.com, bugzilla-daemon@bugzilla.kernel.org,
linux-mm@kvack.org
Subject: Re: [Bug 53501] New: Duplicated MemTotal with different values
Date: Tue, 12 Feb 2013 17:45:42 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1302121742370.5404@chino.kir.corp.google.com> (raw)
In-Reply-To: <20130212165107.32be0c33.akpm@linux-foundation.org>
On Tue, 12 Feb 2013, Andrew Morton wrote:
> > Summary: Duplicated MemTotal with different values
> > Product: Memory Management
> > Version: 2.5
> > Kernel Version: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
> > Platform: All
> > OS/Version: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: Other
> > AssignedTo: akpm@linux-foundation.org
> > ReportedBy: sworddragon2@aol.com
> > Regression: No
> >
> >
> > The installed memory on my system is 16 GiB. /proc/meminfo is showing me
> > "MemTotal: 16435048 kB" but /sys/devices/system/node/node0/meminfo is
> > showing me "Node 0 MemTotal: 16776380 kB".
> >
> > My suggestion: MemTotal in /proc/meminfo should be 16776380 kB too. The old
> > value of 16435048 kB could have its own key "MemAvailable".
>
> hm, mine does that too. A discrepancy between `totalram_pages' and
> NODE_DATA(0)->node_present_pages.
>
> I don't know what the reasons are for that but yes, one would expect
> the per-node MemTotals to sum up to the global one.
>
I'd suspect it has something to do with 9feedc9d831e ("mm: introduce new
field "managed_pages" to struct zone") and 3.8 would be the first kernel
release with this change. Is it possible to try 3.7 or, better yet, with
this patch reverted?
If neither of these are the case, or you aren't comfortable building and
booting a custom kernel, please send along your /proc/zoneinfo.
--
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-02-13 1:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-53501-27@https.bugzilla.kernel.org/>
2013-02-13 0:51 ` Andrew Morton
2013-02-13 1:45 ` David Rientjes [this message]
2013-02-13 3:59 ` Andrew Morton
2013-02-14 3:19 ` David Rientjes
2013-02-14 4:01 ` Jiang Liu
2013-02-15 0:26 ` David Rientjes
2013-02-20 5:21 ` Simon Jeons
2013-02-20 7:09 ` David Rientjes
2013-03-02 2:21 ` Simon Jeons
2013-03-04 11:18 ` David Rientjes
2013-03-04 23:39 ` Simon Jeons
2013-03-05 21:53 ` David Rientjes
2013-02-16 16:27 ` [PATCH 1/2] vm: add 'MemManaged' field to /proc/meminfo and /sys/.../nodex/meminfo Jiang Liu
2013-02-19 21:29 ` David Rientjes
2013-02-20 17:27 ` [PATCH v2] mm: let /proc/meminfo report physical memory installed as "MemTotal" Jiang Liu
2013-02-20 22:49 ` Andrew Morton
2013-02-21 17:26 ` Jiang Liu
2013-02-21 21:31 ` Andrew Morton
2013-02-22 19:22 ` Jiang Liu
2013-02-16 16:27 ` [PATCH 2/2] mm: protect si_meminfo() and si_meminfo_node() from memory hotplug operations Jiang Liu
2013-02-19 21:32 ` David Rientjes
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=alpine.DEB.2.02.1302121742370.5404@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=sworddragon2@aol.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox