[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090504144915.8d0716d7.akpm@linux-foundation.org>
Date: Mon, 4 May 2009 14:49:15 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Wu Fengguang <fengguang.wu@...el.com>
Cc: torvalds@...ux-foundation.org, kosaki.motohiro@...fujitsu.com,
lee.schermerhorn@...com, peterz@...radead.org, riel@...hat.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org, npiggin@...e.de,
cl@...ux-foundation.org
Subject: Re: [RFC][PATCH] vmscan: don't export nr_saved_scan in
/proc/zoneinfo
On Sat, 2 May 2009 10:47:19 +0800
Wu Fengguang <fengguang.wu@...el.com> wrote:
> 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?
>
/proc/zoneinfo is unsalvageable :( Shifting future work over to
/sys/devices/system/node/nodeN/meminfo and deprecating /proc/zoneinfo
sounds good to me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists