From: Simon Jeons <simon.jeons@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Jiang Liu <liuj97@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
sworddragon2@aol.com, bugzilla-daemon@bugzilla.kernel.org,
linux-mm@kvack.org
Subject: Re: [Bug 53501] New: Duplicated MemTotal with different values
Date: Wed, 20 Feb 2013 13:21:12 +0800 [thread overview]
Message-ID: <51245D48.4030102@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1302141624430.27961@chino.kir.corp.google.com>
Hi David,
On 02/15/2013 08:26 AM, David Rientjes wrote:
> On Thu, 14 Feb 2013, Jiang Liu wrote:
>
>>> 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?
>>>
>> Hi David,
>> We have worked out a patch set to address this issue. The first two
>> patches have been merged into v3.8, and another two patches are queued in
>> Andrew's mm tree for v3.9.
>> The patch set introduces a new field named managed_pages into struct
>> zone to distinguish between pages present in a zone and pages managed by the
>> buddy system. So
>> zone->present_pages = zone->spanned_pages - pages_in_hole;
>> zone->managed_pages = pages_managed_by_buddy_system_in_the_zone;
>> We have also added a field named "managed" into /proc/zoneinfo, but
>> haven't touch /proc/meminfo and /sys/devices/system/node/nodex/meminfo yet.
>> If preferred, we could work out another patch to enhance these two files
>> as suggested above.
> I'm glad this is a known issue that you're working on, but my question
> still stands: if MemTotal is going to be consistent throughout
> /proc/meminfo and /sys/devices/system/node/nodeX/meminfo, which is
> correct? The present RAM minus holes or the amount available to the buddy
> allocator not including reserved memory?
What I confuse is why have /proc/meminfo and /proc/vmstat at the same
time, they both use to monitor memory subsystem states. What's the root
reason?
>
> --
> 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>
--
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-20 5:21 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 ` [Bug 53501] New: Duplicated MemTotal with different values Andrew Morton
2013-02-13 1:45 ` David Rientjes
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 [this message]
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=51245D48.4030102@gmail.com \
--to=simon.jeons@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.