On Tue, 12 Feb 2013, Andrew Morton wrote:
> > > > 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?
>
> My desktop machine at google in inconsistent, as is the 2.6.32-based
> machine, so it obviously predates 9feedc9d831e.
>
Hmm, ok. The question is which one is right: the per-node MemTotal is the
amount of present RAM, the spanned range minus holes, and the system
MemTotal is the amount of pages released to the buddy allocator by
bootmem and discounts not only the memory holes but also reserved pages.
Should they both be the amount of RAM present or the amount of unreserved
RAM present?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>