From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <cel@citi.umich.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: RFC: exporting per-superblock statistics to user space
Date: Wed, 23 Mar 2005 11:06:57 +0000 [thread overview]
Message-ID: <20050323110657.GA3745@infradead.org> (raw)
In-Reply-To: <42360D49.7070902@citi.umich.edu>
On Mon, Mar 14, 2005 at 05:16:41PM -0500, Chuck Lever wrote:
> we still have a need to provide "iostat" like statistics for NFS
> clients. attached are a couple of patches, against 2.6.11.3, which
> prototype an approach for providing this kind of data to user programs.
> i'd like some comment on the approach.
>
> 01-mountstats.patch adds a new file called /proc/self/mountstats and a
> new file system hook called show_stats. this just replicates
> /proc/mounts and the show_options hook.
I don't think this makes a lot of sense. The stats aren't per namespace
or mountpoint but per fs-instance, right?
next prev parent reply other threads:[~2005-03-23 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 22:16 RFC: exporting per-superblock statistics to user space Chuck Lever
2005-03-23 11:06 ` Christoph Hellwig [this message]
2005-03-23 13:08 ` Trond Myklebust
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=20050323110657.GA3745@infradead.org \
--to=hch@infradead.org \
--cc=cel@citi.umich.edu \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).