From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: lua extention for wireshak to trace nfs server latencies
Date: Wed, 29 Oct 2014 10:47:41 -0400 [thread overview]
Message-ID: <20141029144741.GA1133@fieldses.org> (raw)
In-Reply-To: <340559201.872226.1414264413792.JavaMail.zimbra@desy.de>
On Sat, Oct 25, 2014 at 09:13:33PM +0200, Mkrtchyan, Tigran wrote:
> recently I was debugging some NFS related issues and
> needed a tool to trace situations when NFS server is slow.
>
> I created a lua extension for tshark which allows to get
> such information, but still has the full power of tshark.
...
> May be some one need's it as well: https://github.com/kofemann/wireshark_lua
>
>
> P.S.: is it the right place for such posts or there yet another mailing list or wiki?
I guess I'd be inclined to cross-post such things to nfsv4@ietf.org. I
don't know how else to reach implementors across OS's.
You're welcome to add things to wiki.linux-nfs.org too.
--b.
prev parent reply other threads:[~2014-10-29 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <74264531.872138.1414263726250.JavaMail.zimbra@desy.de>
2014-10-25 19:13 ` lua extention for wireshak to trace nfs server latencies Mkrtchyan, Tigran
2014-10-29 14:47 ` J. Bruce Fields [this message]
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=20141029144741.GA1133@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tigran.mkrtchyan@desy.de \
/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