From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: net_dropmon usage documentation/examples?
Date: Sun, 7 Apr 2013 11:28:55 +0000 [thread overview]
Message-ID: <20130407112855.GA2544@dcvr.yhbt.net> (raw)
In-Reply-To: <20130406123856.GA11355-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org> wrote:
> On Fri, Apr 05, 2013 at 07:38:55PM +0000, Eric Wong wrote:
> > Hi Neil, I'm wondering if you have or know of any public
> > documentation/examples for using net_dropmon.
> >
> > If not, I'll figure it out on my own at some point.
> >
> > Thanks in advance!
>
> I don't think there are any particular examples at the moment, but if you
> download the dropwatch utility, it uses the dropmon protocol to detect frame
> loss in the stack, and its use is pretty self explanitory, as is the perf script
> that uses the same tracepoints as the dropmon protocol.
>
>
> https://fedorahosted.org/dropwatch/
Thanks Neil! I think I'll just use dropwatch directly instead of
writing my own code, now :)
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-04-07 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 19:38 net_dropmon usage documentation/examples? Eric Wong
2013-04-06 12:38 ` Neil Horman
[not found] ` <20130406123856.GA11355-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2013-04-07 11:28 ` Eric Wong [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=20130407112855.GA2544@dcvr.yhbt.net \
--to=normalperson-rmlxzr9ms24@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.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