From: Benny Halevy <bhalevy@panasas.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
steved@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsstat: reorder nfs4 stats for 2.6.38 and up
Date: Wed, 27 Apr 2011 21:52:53 +0300 [thread overview]
Message-ID: <4DB86605.3000304@panasas.com> (raw)
In-Reply-To: <1303913806.13195.3.camel@lade.trondhjem.org>
On 2011-04-27 17:16, Trond Myklebust wrote:
> On Wed, 2011-04-27 at 07:50 +0300, Benny Halevy wrote:
>> On 2011-04-25 17:11, Chuck Lever wrote:
>>> Hey all-
>>>
>>> So what are we going to do when adding NFSv4.2 to this mix? Will we
>>> then have to freeze both the NFSv4.1 and NFSv4.0 procedure API in the
>>> kernel? Seems painful.
>>
>> Good question.
>> How about changing the stat pseudo-file format to include an op
>> identifier along with its respective counter, printing a line per op?
>
> We already have that in /proc/self/mountstats
>
>
You mean /proc/self/status?
next prev parent reply other threads:[~2011-04-27 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 8:46 [PATCH] nfsstat: reorder nfs4 stats for 2.6.38 and up Benny Halevy
2011-04-25 14:11 ` Chuck Lever
2011-04-27 4:50 ` Benny Halevy
2011-04-27 14:16 ` Trond Myklebust
2011-04-27 18:52 ` Benny Halevy [this message]
2011-04-27 18:58 ` Trond Myklebust
2011-04-27 20:24 ` Benny Halevy
2011-04-27 20:29 ` Trond Myklebust
[not found] ` <1303936194.28589.2.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
2011-04-27 20:33 ` Benny Halevy
2011-04-27 21:05 ` Steve Dickson
2011-05-23 12:39 ` Steve Dickson
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=4DB86605.3000304@panasas.com \
--to=bhalevy@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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).