From: Dave Taht <dave.taht@gmail.com>
To: Justin McCann <jneilm@gmail.com>
Cc: bloat <bloat-devel@lists.bufferbloat.net>
Subject: Re: Dropwatch
Date: Mon, 20 Jun 2011 14:16:13 -0600 [thread overview]
Message-ID: <BANLkTikEzREFwL3_HanFjPmh2DuWFK8vPg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimjeGTBjOoRDjU0SG4yOpL4na_zkA@mail.gmail.com>
On Mon, Jun 20, 2011 at 1:54 PM, Justin McCann <jneilm@gmail.com> wrote:
> I hadn't seen this mentioned here, so maybe I'm not the only one who
> didn't know about it....
I had just got to where net_drop_monitor is configured in the
debloat-testing kernel,
and I think I had got it into cerowrt last week (but need to check)...
>
> I just stumbled across Neil Horman's dropwatch [1], which uses Netlink
> to report which parts of the kernel are dropping packets. It looks
> like the patches made it into the kernel in 2009 [2], and the utility
> is in RHEL 5.6 [3], maybe earlier. The version I tried just reports
> the kernel addresses and doesn't look up the function names directly.
And was casting about for a pre-existing tool to use that
functionality because writing netlink code is a hairy exercise....
seeing what is dropped and why would be very good, at this point.
Thanks for spotting this. It didn't compile on the first try, but
perhaps with some fiddling....
>
> Enjoy,
> Justin
>
>
>
> [1] https://fedorahosted.org/dropwatch/
> [2] http://kerneltrap.org/mailarchive/linux-netdev/2009/3/3/5038664/thread
> [3] http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/5.6_Release_Notes/ar01s03.html
> _______________________________________________
> Bloat-devel mailing list
> Bloat-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat-devel
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
next prev parent reply other threads:[~2011-06-20 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 19:54 Dropwatch Justin McCann
2011-06-20 20:16 ` Dave Taht [this message]
2011-06-20 20:46 ` Dropwatch Dave Taht
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=BANLkTikEzREFwL3_HanFjPmh2DuWFK8vPg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=jneilm@gmail.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