netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Stephen Hemminger <stephen.hemminger@vyatta.com>
Cc: Satoru Moriya <satoru.moriya@hds.com>,
	nhorman@tuxdriver.com, davem@davemloft.net, tgraf@infradead.org,
	Seiji Aguchi <seiji.aguchi@hds.com>,
	dle-develop@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Tracepoint for tcp retransmission
Date: Sun, 18 Dec 2011 01:49:44 +0100	[thread overview]
Message-ID: <20111218004944.GB14903@hell> (raw)
In-Reply-To: <5f654c7d-f18e-4d70-8830-a3e31b8f5f4a@tahiti.vyatta.com>

> Sometimes network packets are dropped for some reason. In enterprise
> systems which require strict RAS functionality, we must know the
> reason why it happened and explain it to our customers even if using
> TCP. When we investigate the incidents, at first we try to find out
> whether the problem is in the server(kernel, application) or else
> (router, hub etc). And next we try to find out which layer
> (application/middleware/kernel(IP/TCP/UDP/..)etc.) the problem
> occurs.

For the first question tcpdump may the right tool. For the later systemtap can
be used. I mean we now have the possibility to instrument the kernel at runtime,
without bloating the source. Anyway: is 63e03724b51 not suitable to gather the
required information easily?

Hagen

  reply	other threads:[~2011-12-18  0:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 22:14 [PATCH 0/2] Tracepoint for tcp retransmission Satoru Moriya
2011-12-16 22:16 ` [PATCH 1/2] tcp: refactor tcp_retransmit_skb() for a single return point Satoru Moriya
2011-12-19 12:10   ` David Laight
2011-12-20 16:55     ` Satoru Moriya
2011-12-16 22:17 ` [PATCH 2/2] tcp: add tracepoint for tcp retransmission Satoru Moriya
2011-12-17  0:17 ` [PATCH 0/2] Tracepoint " Stephen Hemminger
2011-12-18  0:49   ` Hagen Paul Pfeifer [this message]
2011-12-20 23:40     ` Satoru Moriya
2011-12-21  7:05       ` Eric Dumazet
2011-12-20 18:13   ` Satoru Moriya

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=20111218004944.GB14903@hell \
    --to=hagen@jauu.net \
    --cc=davem@davemloft.net \
    --cc=dle-develop@lists.sourceforge.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).