linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: David Rientjes <rientjes@google.com>
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 09:57:37 +0100	[thread overview]
Message-ID: <20170317085737.GE26298@dhcp22.suse.cz> (raw)
In-Reply-To: <20170308144159.GD11034@dhcp22.suse.cz>

On Wed 08-03-17 15:41:59, Michal Hocko wrote:
> On Fri 03-03-17 14:53:07, David Rientjes wrote:
> > Initscripts can use the information (protection levels) from
> > /proc/zoneinfo to configure vm.lowmem_reserve_ratio at boot.
> > 
> > vm.lowmem_reserve_ratio is an array of ratios for each configured zone on
> > the system.  If a zone is not populated on an arch, /proc/zoneinfo
> > suppresses its output.
> > 
> > This results in there not being a 1:1 mapping between the set of zones
> > emitted by /proc/zoneinfo and the zones configured by
> > vm.lowmem_reserve_ratio.
> >
> > This patch shows statistics for non-populated zones in /proc/zoneinfo.
> > The zones exist and hold a spot in the vm.lowmem_reserve_ratio array.
> > Without this patch, it is not possible to determine which index in the
> > array controls which zone if one or more zones on the system are not
> > populated.
> > 
> > Remaining users of walk_zones_in_node() are unchanged.  Files such as
> > /proc/pagetypeinfo require certain zone data to be initialized properly
> > for display, which is not done for unpopulated zones.
> 
> 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?
> 
> I can see how skipping empty zones completely can be clumsy but wouldn't
> it be sufficient to just provide
> 
> Node $NUM, zone $NAME
> (unpopulated)
> 
> instead?

ping
-- 
Michal Hocko
SUSE Labs

--
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>

  reply	other threads:[~2017-03-17  8:57 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 [this message]
2017-03-17 21:21           ` David Rientjes
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=20170317085737.GE26298@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --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=rientjes@google.com \
    --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