|author||Wu Fengguang <email@example.com>||2009-06-16 15:32:30 -0700|
|committer||Linus Torvalds <firstname.lastname@example.org>||2009-06-16 19:47:39 -0700|
vmscan: don't export nr_saved_scan in /proc/zoneinfo
The lru->nr_saved_scan's are not meaningful counters for even kernel developers. They typically are smaller than 32 and are always 0 for large lists. So remove them from /proc/zoneinfo. Hopefully this interface change won't break too many scripts. /proc/zoneinfo is too unstructured to be script friendly, and I wonder the affected scripts - if there are any - are still bleeding since the not long ago commit "vmscan: split LRU lists into anon & file sets", which also touched the "scanned" line :) If we are to re-export accumulated vmscan counts in the future, they can go to new lines in /proc/zoneinfo instead of the current form, or to /sys/devices/system/node/node0/meminfo? Signed-off-by: Wu Fengguang <email@example.com> Acked-by: Rik van Riel <firstname.lastname@example.org> Cc: Nick Piggin <email@example.com> Acked-by: Christoph Lameter <firstname.lastname@example.org> Cc: Peter Zijlstra <email@example.com> Cc: KOSAKI Motohiro <firstname.lastname@example.org> Signed-off-by: Andrew Morton <email@example.com> Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
1 files changed, 1 insertions, 5 deletions
diff --git a/mm/vmstat.c b/mm/vmstat.c
index 84c05555691..1e151cf6bf8 100644
@@ -710,7 +710,7 @@ static void zoneinfo_show_print(struct seq_file *m, pg_data_t *pgdat,
"\n min %lu"
"\n low %lu"
"\n high %lu"
- "\n scanned %lu (aa: %lu ia: %lu af: %lu if: %lu)"
+ "\n scanned %lu"
"\n spanned %lu"
"\n present %lu",
@@ -718,10 +718,6 @@ static void zoneinfo_show_print(struct seq_file *m, pg_data_t *pgdat,