From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Satoru Moriya <satoru.moriya@hds.com>, <netdev@vger.kernel.org>,
Seiji Aguchi <seiji.aguchi@hds.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 1/2] udp: add tracepoints for queueing skb to rcvbuf
Date: Tue, 21 Jun 2011 16:48:39 +0200 [thread overview]
Message-ID: <5b828bb3667480edda9a4a77918007ee@localhost> (raw)
In-Reply-To: <20110621135009.GD16311@hmsreliant.think-freely.org>
On Tue, 21 Jun 2011 09:50:09 -0400, Neil Horman wrote:
> I hadn't really thought about that much, but yes, I suppose I could
migrate
> dropwatch to export kfree_skb data via perf. Admittedly I don't know
much
> about
> the perf api. Do you have any pointers on its use (to save me time in
> figuring
> out how it all works)? If so I'll start looking into it.
http://git.kernel.org/?p=status/powertop/powertop.git;a=tree;f=perf;hb=HEAD
is probably a good starting point. Especially
perf_bundle.cpp:handle_trace_point(). But I am not sure if this is the most
clever way. The direct us of the perf api is somewhat dodgy (not sure if
the ABI will change). IIRC Steven Rostedt wrote about a user space library
(I CC'ed Steven). BUT: tracing via /sys/kernel/debug/tracing/* may be
enough, eventually there is no need for perf at all. Then trace-cmd may
provide some nice ideas how to wrap the /sys/kernel/debug/tracing interface
programmatically.
The idea behind dropwatch is great! There is currently to much
unconsolidated information. It takes a genius to understand where and later
why packets are dropped. A userspace tool where no kernel patch is required
is a big plus! ;-)
Hagen
next prev parent reply other threads:[~2011-06-21 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 21:56 [PATCH 0/2] Tracepoints for queueing skb to rcvbuf Satoru Moriya
2011-06-17 21:58 ` [PATCH 1/2] udp: add tracepoints " Satoru Moriya
2011-06-21 10:47 ` Neil Horman
2011-06-21 11:58 ` Hagen Paul Pfeifer
2011-06-21 13:50 ` Neil Horman
2011-06-21 14:48 ` Hagen Paul Pfeifer [this message]
2011-06-21 17:14 ` Steven Rostedt
2011-06-17 22:00 ` [PATCH 2/2] core: " Satoru Moriya
2011-06-21 10:48 ` Neil Horman
2011-06-21 23:07 ` [PATCH 0/2] Tracepoints " David Miller
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=5b828bb3667480edda9a4a77918007ee@localhost \
--to=hagen@jauu.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=rostedt@goodmis.org \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.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;
as well as URLs for NNTP newsgroup(s).