summaryrefslogtreecommitdiffstats
path: root/mm/kmemleak-test.c
diff options
context:
space:
mode:
authorWu Fengguang <fengguang.wu@intel.com>2009-06-16 15:32:30 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2009-06-16 19:47:39 -0700
commit08d9ae7cbbd0c5c07573d072ec771e997a9a39e0 (patch)
treee669cd3eb5a84842c798af936c9e5642765b556f /mm/kmemleak-test.c
parent6e08a369ee10b361ac1cdcdf4fabd420fd08beb3 (diff)
downloadblackbird-op-linux-08d9ae7cbbd0c5c07573d072ec771e997a9a39e0.tar.gz
blackbird-op-linux-08d9ae7cbbd0c5c07573d072ec771e997a9a39e0.zip
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 <fengguang.wu@intel.com> Acked-by: Rik van Riel <riel@redhat.com> Cc: Nick Piggin <npiggin@suse.de> Acked-by: Christoph Lameter <cl@linux-foundation.org> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/kmemleak-test.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud