From: Satoru Moriya <satoru.moriya@hds.com>
To: Neil Horman <nhorman@tuxdriver.com>,
"Frank Ch. Eigler" <fche@redhat.com>
Cc: Hagen Paul Pfeifer <hagen@jauu.net>,
"Frank Ch. Eigler" <fche@elastic.org>,
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" <fche@sourceware.org>,
"mathieu.desnoyers@polymtl.ca" <mathieu.desnoyers@polymtl.ca>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: RE: [PATCH v2 0/2] Tracepoint for tcp retransmission
Date: Mon, 6 Feb 2012 13:21:37 -0500 [thread overview]
Message-ID: <65795E11DBF1E645A09CEC7EAEE94B9CB8E7B0D4@USINDEVS02.corp.hds.com> (raw)
In-Reply-To: <20120206155305.GB3620@hmsreliant.think-freely.org>
On 02/06/2012 10:53 AM, Neil Horman wrote:
> On Mon, Feb 06, 2012 at 10:20:19AM -0500, Frank Ch. Eigler wrote:
>> On Sun, Feb 05, 2012 at 08:32:47PM -0500, Neil Horman wrote:
>>
> Yes, that was his point. Mine was that, given Satoru's needs, a
> netfilter hook provides 90% of what they need (as its been described
> here). If you're unfamiliar with them, netfilter hooks are those
> standard points in the network input/output/forwarding paths at which
> we can watch and maniupulate network traffic. They're what
> iptables/ip6tables/ebtables/etc use to do everything they do. I'm
> suggesting that they use those existing hooks to monitor outgoing
> traffic for whatever information they want (in this case
> retransmitted unacked tcp sequence numbers). Or whatever else their
> interested in.
>
> As for the other 10% (recording failed retransmits, which don't
> generate traffic), we have existing tracepoints that can be used.
Thank you so much, Neil and other guys.
For now it seems to be difficult to move into netfilter approach
because "other 10%" is so important for us. But first, I'll consider
it more deeply.
Regards,
Satoru
next prev parent reply other threads:[~2012-02-06 18:22 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
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 [this message]
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=65795E11DBF1E645A09CEC7EAEE94B9CB8E7B0D4@USINDEVS02.corp.hds.com \
--to=satoru.moriya@hds.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=fche@sourceware.org \
--cc=hagen@jauu.net \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=rostedt@goodmis.org \
--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).