From: "Frank Ch. Eigler" <fche@elastic.org>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Hagen Paul Pfeifer <hagen@jauu.net>,
Satoru Moriya <satoru.moriya@hds.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"tgraf@infradead.org" <tgraf@infradead.org>,
"stephen.hemminger@vyatta.com" <stephen.hemminger@vyatta.com>,
"eric.dumazet@gmail.com" <eric.dumazet@gmail.com>,
Seiji Aguchi <seiji.aguchi@hds.com>,
fche@sourceware.org
Subject: Re: [PATCH v2 0/2] Tracepoint for tcp retransmission
Date: Sun, 5 Feb 2012 07:53:25 -0500 [thread overview]
Message-ID: <20120205125325.GA31578@elastic.org> (raw)
In-Reply-To: <20120204200937.GA2670@neilslaptop.think-freely.org>
Hi -
On Sat, Feb 04, 2012 at 03:09:37PM -0500, Neil Horman wrote:
> [...]
> Systemtap is fine for development. Lots of application/product
> vendors really don't like it. On top of the difficult to use
> aspect
(Just curious, what difficulty-to-use aspect have you more recently
come across?)
> it requires that debugging stabs info be kept with the kernel, which
> is a real pain, especially if you're running on a stable kernel.
> [...]
You probably mean when running on an unstable kernel, no? Installing
debuginfo for a stable kernel is a one-time event. It also enables
"perf probe" and crash(8) and other tools. Plus, with systemtap,
there are two separate network-remoting mechanisms (--use-server
compilation and --remote execution) that make local debuginfo
unnecessary.
Anyway, a reasonable way to go may be to prototype in stap whatever
hard-coded kernel module y'all envision finally doing this work.
- FChE
next prev parent reply other threads:[~2012-02-05 13:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 18:07 [PATCH v2 0/2] Tracepoint for tcp retransmission Satoru Moriya
2012-01-20 18:08 ` [PATCH v2 1/2] tcp: refactor tcp_retransmit_skb() for a single return point Satoru Moriya
2012-01-20 18:09 ` [PATCH v2 2/2] tcp: add tracepoint for tcp retransmission Satoru Moriya
2012-01-20 18:50 ` [PATCH v2 0/2] Tracepoint " David Miller
2012-02-03 21:47 ` Satoru Moriya
2012-02-04 4:40 ` Yuchung Cheng
2012-02-06 18:32 ` Satoru Moriya
2012-02-04 14:28 ` Neil Horman
2012-02-04 15:58 ` Hagen Paul Pfeifer
2012-02-04 20:09 ` Neil Horman
2012-02-05 12:53 ` Frank Ch. Eigler [this message]
2012-02-05 19:17 ` Neil Horman
2012-02-05 20:04 ` Hagen Paul Pfeifer
2012-02-05 21:48 ` David Miller
2012-02-06 1:32 ` Neil Horman
2012-02-06 15:20 ` Frank Ch. Eigler
2012-02-06 15:24 ` Eric Dumazet
2012-02-06 15:38 ` Neil Horman
2012-02-06 15:53 ` Neil Horman
2012-02-06 16:18 ` Steven Rostedt
2012-02-06 17:02 ` Eric Dumazet
2012-02-06 17:18 ` Steven Rostedt
2012-02-06 16:21 ` Frank Ch. Eigler
2012-02-06 18:21 ` Satoru Moriya
2012-01-25 13:27 ` Hagen Paul Pfeifer
2012-01-25 14:44 ` Eric Dumazet
2012-01-26 18:51 ` David Miller
2012-02-03 20:31 ` Satoru Moriya
2012-02-03 20:43 ` Satoru Moriya
2012-02-03 20:55 ` Hagen Paul Pfeifer
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=20120205125325.GA31578@elastic.org \
--to=fche@elastic.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fche@sourceware.org \
--cc=hagen@jauu.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=stephen.hemminger@vyatta.com \
--cc=tgraf@infradead.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;
as well as URLs for NNTP newsgroup(s).