From: David Rientjes <rientjes@google.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch v2] mm, vmstat: print non-populated zones in zoneinfo
Date: Fri, 17 Mar 2017 14:21:12 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1703171416070.81333@chino.kir.corp.google.com> (raw)
In-Reply-To: <20170317085737.GE26298@dhcp22.suse.cz>
On Fri, 17 Mar 2017, Michal Hocko wrote:
> > Does it really make sense to print any counters of that zone though?
> > Your follow up patch just suggests that we don't want some but what
> > about others?
> >
Managed and present pages needs to be emitted for userspace parsing of
memory hotplug, I chose not to suppress the five or six other members
since the risk of breaking existing parsers far outweighs any savings from
not emitting these lines. There is already plenty of opportunities to
clean /proc/zoneinfo up as described by Andrew that may be possible but
care needs to taken to ensure we don't break existing readers.
next prev parent reply other threads:[~2017-03-17 21:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 23:26 [patch] mm, zoneinfo: print non-populated zones David Rientjes
2017-03-03 13:35 ` Anshuman Khandual
2017-03-03 22:46 ` David Rientjes
2017-03-03 22:53 ` [patch v2] mm, vmstat: print non-populated zones in zoneinfo David Rientjes
2017-03-04 8:21 ` Anshuman Khandual
2017-03-06 22:03 ` [patch -mm] mm, vmstat: suppress pcp stats for unpopulated " David Rientjes
2017-03-06 22:11 ` Andrew Morton
2017-03-08 14:42 ` [patch v2] mm, vmstat: print non-populated " Michal Hocko
2017-03-17 8:57 ` Michal Hocko
2017-03-17 21:21 ` David Rientjes [this message]
2017-05-03 23:41 ` [PATCH] mm, vmstat: Remove spurious WARN() during zoneinfo print Reza Arbab
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.10.1703171416070.81333@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=vbabka@suse.cz \
/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).