From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH] perf: Add drop monitor script
Date: Wed, 13 Jul 2011 23:20:42 +0200 [thread overview]
Message-ID: <1310592042.2586.43.camel@twins> (raw)
In-Reply-To: <20110713192316.GA12498@hmsreliant.think-freely.org>
On Wed, 2011-07-13 at 15:23 -0400, Neil Horman wrote:
> On Mon, Jul 04, 2011 at 01:40:17PM -0400, Neil Horman wrote:
> > A while back I created the dropmonitor protocol, which allowed users to get
> > reports of dropped frames communicated to them via a netlink socket. While
> > useful, several people have now asked that I integrate the ability to do drop
> > monitoring with perf, so they don't have to run additional tools. This patch
> > adds a drop monitor script to the perf suite, and provides the same output that
> > the netlink socket does.
> >
> > Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> > CC: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > CC: Paul Mackerras <paulus@samba.org>
> > CC: Ingo Molnar <mingo@elte.hu>
> > CC: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
> Ping guys, any feedback on this?
I don't speak snake, nor really condone snake speak. You'll have to wait
until acme is back from holidays.
next prev parent reply other threads:[~2011-07-13 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 17:40 [PATCH] perf: Add drop monitor script Neil Horman
2011-07-13 19:23 ` Neil Horman
2011-07-13 21:20 ` Peter Zijlstra [this message]
2011-07-25 13:25 ` Neil Horman
2011-07-25 15:03 ` Arnaldo Carvalho de Melo
2011-07-25 17:47 ` Neil Horman
2011-08-29 10:48 ` Neil Horman
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=1310592042.2586.43.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nhorman@tuxdriver.com \
--cc=paulus@samba.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