From: Chuck Lever <chuck.lever@oracle.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: neilb@suse.de, jengelh@computergmbh.de, kzak@redhat.com,
akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, util-linux-ng@vger.kernel.org,
linuxram@us.ibm.com, viro@ftp.linux.org.uk, hch@infradead.org,
a.p.zijlstra@chello.nl
Subject: Re: [patch] VFS: extend /proc/mounts
Date: Thu, 17 Jan 2008 10:36:24 -0500 [thread overview]
Message-ID: <88976638-FBF2-45CB-9ED3-500ED2623916@oracle.com> (raw)
In-Reply-To: <E1JFQWv-00061b-QA@pomaz-ex.szeredi.hu>
On Jan 17, 2008, at 3:55 AM, Miklos Szeredi wrote:
>> Hey, I just found /proc/X/mountstats. How does this fit in to the
>> big
>> picture?
>
> It seems to show some counters for NFS mounts, no other filesystem
> uses it. Format looks rather less nice, than /proc/X/mounts (why do
> we need long english sentences under /proc?).
I introduced /proc/self/mountstats because we need a way for non-
block-device-based file systems to report I/O statistics. Everything
else I tried was rejected, and apparently what we ended up with was
reviewed by only a handful of people, so no one else likes it or uses
it.
It can go away for all I care, as long as we retain some flexible
mechanism for non-block-based file systems to report I/O stats. As
far as I am aware, there are only two user utilities that understand
and parse this data, and I maintain both.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2008-01-17 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 22:12 Miklos Szeredi
2008-01-16 22:30 ` Andrew Morton
2008-01-16 23:15 ` Miklos Szeredi
2008-01-16 23:43 ` Karel Zak
2008-01-16 23:58 ` Jan Engelhardt
2008-01-17 0:09 ` Andrew Morton
2008-01-17 3:35 ` Al Viro
2008-01-17 0:33 ` Neil Brown
2008-01-17 1:17 ` Jan Engelhardt
2008-01-17 8:55 ` Miklos Szeredi
2008-01-17 15:36 ` Chuck Lever [this message]
2008-01-17 2:45 ` H. Peter Anvin
2008-01-17 3:33 ` Al Viro
2008-01-17 8:36 ` Miklos Szeredi
2008-01-17 10:34 ` Karel Zak
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=88976638-FBF2-45CB-9ED3-500ED2623916@oracle.com \
--to=chuck.lever@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jengelh@computergmbh.de \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=miklos@szeredi.hu \
--cc=neilb@suse.de \
--cc=util-linux-ng@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®