From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Lans Carstensen <Lans.Carstensen@dreamworks.com>,
NFS list <linux-nfs@vger.kernel.org>
Subject: Re: [NFS] [PATCH] nfs-utils: nfs-iostat.py option to sort by ops/s
Date: Tue, 25 Aug 2009 13:34:01 -0400 [thread overview]
Message-ID: <4A942089.1010102@RedHat.com> (raw)
In-Reply-To: <009376AC-B08B-4E90-A46B-E5BC069A5A78@oracle.com>
On 08/25/2009 12:29 PM, Chuck Lever wrote:
> [ Cc: changed to correct mailing list. sf.net list is deprecated. ]
>
> On Aug 24, 2009, at 7:24 PM, Lans Carstensen wrote:
>> Hi,
>>
>> I've recently made tools/nfs-iostat/nfs-iostat.py more useful in our
>> autofs environment with a variety of cleanups and am offering this
>> patch up for discussion and/or inclusion in nfs-utils. It does the
>> following:
>>
>> * Adds a --top flag to sort the display of mountpoint entries by ops/s.
>> * Adds a --<n> flag to only display stats for the first <n> mountpoints
>> * Re-reads the mountpoint list on intervals since it's dynamic in an
>> autofs environment.
>> * Conforms the Python path to the LSB 3.2+ standard of /usr/bin/python
>> http://refspecs.freestandards.org/LSB_3.2.0/LSB-Languages/LSB-Languages/pylocation.html
>>
>
> A couple of overall comments.
>
> 1. These seem to be logically independent changes, so we would prefer
> them in separate patches. Each logical change can be refined and voted
> up or down separately.
I guess you could break this up into more patches... but overall its
by no means unruly....
>
> 2. Sorting by ops is OK, but not sure about "--top". Since the script
> doesn't generate a curses like display like "top" does, maybe "--sort
> <n>" would be a better name, and --top and --<n> could be combined.
Hmm.. I kinda like like the --top flag... its pretty descriptive to
what it does..
>
> 3. The distributors should weigh in on the Python path change.
Using '#!/usr/bin/python' is better than '#!/usr/bin/env python'
since you know exactly which python binary you will be using.
It was also pointed out the env convention will confuse
rpm's dependency generator
steved.
next prev parent reply other threads:[~2009-08-25 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 23:24 [NFS] [PATCH] nfs-utils: nfs-iostat.py option to sort by ops/s Lans Carstensen
2009-08-25 16:29 ` Chuck Lever
2009-08-25 17:34 ` Steve Dickson [this message]
2009-08-25 17:48 ` Chuck Lever
2009-08-25 18:36 ` Lans Carstensen
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=4A942089.1010102@RedHat.com \
--to=steved@redhat.com \
--cc=Lans.Carstensen@dreamworks.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@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