From: David Rientjes <rientjes@google.com> Date: 2017-03-03 02:25:13
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.
Signed-off-by: David Rientjes <rientjes@google.com>
---
mm/vmstat.c | 22 +++++++++++++---------
1 file changed, 13 insertions(+), 9 deletions(-)
@@ -1121,8 +1121,12 @@ static void frag_stop(struct seq_file *m, void *arg){}-/* Walk all the zones in a node and print using a callback */+/*+*Walkzonesinanodeandprintusingacallback.+*If@populatedistrue,onlyusecallbackforzonesthatarepopulated.+*/staticvoidwalk_zones_in_node(structseq_file*m,pg_data_t*pgdat,+boolpopulated,void(*print)(structseq_file*m,pg_data_t*,structzone*)){structzone*zone;
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>
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.
Right, its a problem when it does not even display array elements with
an index value associated with it. But changing the array display will
break the interface where as displaying non populated zones in the
/proc/zoneinfo does not break anything.
quoted hunk
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.
Signed-off-by: David Rientjes <rientjes@google.com>
---
mm/vmstat.c | 22 +++++++++++++---------
1 file changed, 13 insertions(+), 9 deletions(-)
@@ -1121,8 +1121,12 @@ static void frag_stop(struct seq_file *m, void *arg){}-/* Walk all the zones in a node and print using a callback */+/*+*Walkzonesinanodeandprintusingacallback.+*If@populatedistrue,onlyusecallbackforzonesthatarepopulated.+*/staticvoidwalk_zones_in_node(structseq_file*m,pg_data_t*pgdat,+boolpopulated,void(*print)(structseq_file*m,pg_data_t*,structzone*)){structzone*zone;
The name of the Boolean "populated" is bit misleading IMHO. What I think you
want here is to invoke the callback if the zone is populated as well as this
variable is true. The variable can be named something like 'assert_populated'.
--
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>
From: David Rientjes <rientjes@google.com> Date: 2017-03-03 22:46:07
On Fri, 3 Mar 2017, Anshuman Khandual wrote:
quoted
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.
Right, its a problem when it does not even display array elements with
an index value associated with it. But changing the array display will
break the interface where as displaying non populated zones in the
/proc/zoneinfo does not break anything.
Precisely.
The name of the Boolean "populated" is bit misleading IMHO. What I think you
want here is to invoke the callback if the zone is populated as well as this
variable is true. The variable can be named something like 'assert_populated'.
I like it, I'll send a v2. Thanks.
--
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>
From: David Rientjes <rientjes@google.com> Date: 2017-03-03 22:53:11
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.
Signed-off-by: David Rientjes <rientjes@google.com>
---
v2: - s/bool populated/b assert_populated/ per Anshuman
- add comment to zoneinfo_show() to describe why we care
mm/vmstat.c | 27 +++++++++++++++++----------
1 file changed, 17 insertions(+), 10 deletions(-)
@@ -1121,8 +1121,12 @@ static void frag_stop(struct seq_file *m, void *arg){}-/* Walk all the zones in a node and print using a callback */+/*+*Walkzonesinanodeandprintusingacallback.+*If@assert_populatedistrue,onlyusecallbackforzonesthatarepopulated.+*/staticvoidwalk_zones_in_node(structseq_file*m,pg_data_t*pgdat,+boolassert_populated,void(*print)(structseq_file*m,pg_data_t*,structzone*)){structzone*zone;
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>
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.
Signed-off-by: David Rientjes <rientjes@google.com>
Reviewed-by: Anshuman Khandual <redacted>
--
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>
From: David Rientjes <rientjes@google.com> Date: 2017-03-06 22:10:13
After "mm, vmstat: print non-populated zones in zoneinfo", /proc/zoneinfo
will show unpopulated zones.
The per-cpu pageset statistics are not relevant for unpopulated zones and
can be potentially lengthy, so supress them when they are not interesting.
Also moves lowmem reserve protection information above pcp stats since it
is relevant for all zones per vm.lowmem_reserve_ratio.
Signed-off-by: David Rientjes <rientjes@google.com>
---
mm/vmstat.c | 20 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
@@ -1392,18 +1392,24 @@ static void zoneinfo_show_print(struct seq_file *m, pg_data_t *pgdat,zone->present_pages,zone->managed_pages);-for(i=0;i<NR_VM_ZONE_STAT_ITEMS;i++)-seq_printf(m,"\n %-12s %lu",vmstat_text[i],-zone_page_state(zone,i));-seq_printf(m,"\n protection: (%ld",zone->lowmem_reserve[0]);for(i=1;i<ARRAY_SIZE(zone->lowmem_reserve);i++)seq_printf(m,", %ld",zone->lowmem_reserve[i]);-seq_printf(m,-")"-"\n pagesets");+seq_putc(m,')');++/* If unpopulated, no other information is useful */+if(!populated_zone(zone)){+seq_putc(m,'\n');+return;+}++for(i=0;i<NR_VM_ZONE_STAT_ITEMS;i++)+seq_printf(m,"\n %-12s %lu",vmstat_text[i],+zone_page_state(zone,i));++seq_printf(m,"\n pagesets");for_each_online_cpu(i){structper_cpu_pageset*pageset;--
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>
From: Andrew Morton <akpm@linux-foundation.org> Date: 2017-03-06 22:21:40
On Mon, 6 Mar 2017 14:03:32 -0800 (PST) David Rientjes [off-list ref] wrote:
After "mm, vmstat: print non-populated zones in zoneinfo", /proc/zoneinfo
will show unpopulated zones.
The per-cpu pageset statistics are not relevant for unpopulated zones and
can be potentially lengthy, so supress them when they are not interesting.
Also moves lowmem reserve protection information above pcp stats since it
is relevant for all zones per vm.lowmem_reserve_ratio.
Well it's not strictly back-compatible, but /proc/zoneinfo is such a
mess that parsers will be few and hopefully smart enough to handle
this.
btw,
pagesets
cpu: 0
count: 118
high: 186
batch: 31
vm stats threshold: 72
cpu: 1
count: 53
high: 186
batch: 31
vm stats threshold: 72
Should the "vm stats threshold" thing be indented further?
Do we need to print it out N times anyway? Can different CPUs have
different values?
--
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>
From: Michal Hocko <mhocko@kernel.org> Date: 2017-03-08 14:53:52
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?
quoted hunk
Signed-off-by: David Rientjes <rientjes@google.com>
---
v2: - s/bool populated/b assert_populated/ per Anshuman
- add comment to zoneinfo_show() to describe why we care
mm/vmstat.c | 27 +++++++++++++++++----------
1 file changed, 17 insertions(+), 10 deletions(-)
@@ -1121,8 +1121,12 @@ static void frag_stop(struct seq_file *m, void *arg){}-/* Walk all the zones in a node and print using a callback */+/*+*Walkzonesinanodeandprintusingacallback.+*If@assert_populatedistrue,onlyusecallbackforzonesthatarepopulated.+*/staticvoidwalk_zones_in_node(structseq_file*m,pg_data_t*pgdat,+boolassert_populated,void(*print)(structseq_file*m,pg_data_t*,structzone*)){structzone*zone;
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>
--
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>
From: Michal Hocko <mhocko@kernel.org> Date: 2017-03-17 08:58:11
On Wed 08-03-17 15:41:59, Michal Hocko wrote:
On Fri 03-03-17 14:53:07, David Rientjes wrote:
quoted
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>
From: David Rientjes <rientjes@google.com> Date: 2017-03-17 21:21:16
On Fri, 17 Mar 2017, Michal Hocko wrote:
quoted
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.
--
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>
After "mm, vmstat: print non-populated zones in zoneinfo",
/proc/zoneinfo will show unpopulated zones.
A memoryless node, having no populated zones at all, was previously
ignored, but will now trigger the WARN() in is_zone_first_populated().
Remove this warning, as its only purpose was to warn of a situation that
has since been enabled.
Signed-off-by: Reza Arbab <redacted>
---
Aside: The "per-node stats" are still printed under the first populated
zone, but that's not necessarily the first stanza any more. I'm not sure
which criteria is more important with regard to not breaking parsers, but
it looks a little weird to the eye.
mm/vmstat.c | 2 --
1 file changed, 2 deletions(-)
@@ -1359,8 +1359,6 @@ static bool is_zone_first_populated(pg_data_t *pgdat, struct zone *zone)returnzone==compare;}-/* The zone must be somewhere! */-WARN_ON_ONCE(1);returnfalse;}
--
1.8.3.1
--
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>