From: Christoph Lameter <cl@linux.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Wu Fengguang <fengguang.wu@intel.com>,
torvalds@linux-foundation.org, kosaki.motohiro@jp.fujitsu.com,
lee.schermerhorn@hp.com, riel@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, npiggin@suse.de
Subject: Re: [RFC][PATCH] vmscan: don't export nr_saved_scan in /proc/zoneinfo
Date: Tue, 5 May 2009 11:43:58 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0905051142580.11830@qirst.com> (raw)
In-Reply-To: <1241509090.11059.31.camel@twins>
On Tue, 5 May 2009, Peter Zijlstra wrote:
> > /proc/zoneinfo is unsalvageable :( Shifting future work over to
> > /sys/devices/system/node/nodeN/meminfo and deprecating /proc/zoneinfo
> > sounds good to me.
>
> If only one could find things put in sysfs :-)
Write a "zoneinfo" command line tool to show this information? If we
cannot output large texts via /proc or /sys then we need small tools for
all sorts of statistics.
--
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>
next prev parent reply other threads:[~2009-05-05 15:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200904302208.n3UM8t9R016687@imap1.linux-foundation.org>
2009-05-01 1:22 ` [patch 20/22] vmscan: avoid multiplication overflow in shrink_zone() Wu Fengguang
2009-05-01 2:49 ` Andrew Morton
2009-05-01 6:29 ` Wu Fengguang
2009-05-02 2:31 ` [PATCH] vmscan: cleanup the scan batching code Wu Fengguang
2009-05-02 2:47 ` [RFC][PATCH] vmscan: don't export nr_saved_scan in /proc/zoneinfo Wu Fengguang
2009-05-02 14:21 ` Rik van Riel
2009-05-04 13:50 ` Christoph Lameter
2009-05-04 14:40 ` KOSAKI Motohiro
2009-05-04 21:49 ` Andrew Morton
2009-05-05 7:38 ` Peter Zijlstra
2009-05-05 15:43 ` Christoph Lameter [this message]
2009-05-02 14:14 ` [PATCH] vmscan: cleanup the scan batching code Rik van Riel
2009-05-04 8:26 ` Peter Zijlstra
2009-05-04 14:41 ` KOSAKI Motohiro
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=alpine.DEB.1.10.0905051142580.11830@qirst.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.org \
/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