From: Satoru Moriya <satoru.moriya@hds.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Hagen Paul Pfeifer <hagen@jauu.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
"tgraf@infradead.org" <tgraf@infradead.org>,
Stephen Hemminger <stephen.hemminger@vyatta.com>,
Seiji Aguchi <seiji.aguchi@hds.com>
Subject: RE: [PATCH v2 0/2] Tracepoint for tcp retransmission
Date: Fri, 3 Feb 2012 15:31:48 -0500 [thread overview]
Message-ID: <65795E11DBF1E645A09CEC7EAEE94B9CB8D3EA36@USINDEVS02.corp.hds.com> (raw)
In-Reply-To: <1327502660.2425.60.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
On 01/25/2012 09:44 AM, Eric Dumazet wrote:
> Agreed, but last time I tried systemtap I failed miserably.
> It was on a debian distro.
>
> Anyway, it seems we lack a LINUX_MIB_TCPRETRANSFAIL counter.
>
> "netstat -s" is an incredible universal tool.
>
> [PATCH net-next] tcp: add LINUX_MIB_TCPRETRANSFAIL counter
>
> It might be useful to get a counter of failed tcp_retransmit_skb()
> calls.
Thank you, Eric.
This is a good first step for us to grab the failure of
retransmission. But unfortunately, it's not enough because
when we analyze incidents and report to our customers,
we need more detailed information such as when it happened,
why it failed etc.
Therefore I proposed this tracepoint.
Regards,
Satoru
next prev parent reply other threads:[~2012-02-03 20:32 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
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 [this message]
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=65795E11DBF1E645A09CEC7EAEE94B9CB8D3EA36@USINDEVS02.corp.hds.com \
--to=satoru.moriya@hds.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hagen@jauu.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).