From: Rick Jones <rick.jones2@hp.com>
To: "Dan Noé" <dnoe@limebrokerage.com>
Cc: netdev@vger.kernel.org
Subject: Re: Detecting TCP loss on the receiving side?
Date: Thu, 10 Jul 2008 14:14:18 -0700 [thread overview]
Message-ID: <48767BAA.3090704@hp.com> (raw)
In-Reply-To: <48766EC2.2090000@limebrokerage.com>
Dan Noé wrote:
> Rick Jones wrote:
>
>> If this is just for troubleshooting, why not just take a tcpdump trace?
>
>
> We're pushing a lot of data.. several Mbps pretty much all day long..
> and the (suspected) loss occurs sporadically. Ideally we'd like to be
> able to easily correlate it with latency seen in our app.
If your app can already log a timestamped "high latency" warning, then
it would simply be a matter of a big disc and comparing timestamps in
the tcpdump trace :)
Also, it appears that for what you want, you only need to capture up
through the TCP header, so while it may be many Mbit/s on the wire, it
will be fewer Mbit/s in the trace.
rick jones
next prev parent reply other threads:[~2008-07-10 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 19:44 Detecting TCP loss on the receiving side? Dan Noé
2008-07-10 20:11 ` Rick Jones
2008-07-10 20:19 ` Dan Noé
2008-07-10 21:05 ` John Heffner
2008-07-10 21:20 ` Rick Jones
2008-07-10 21:34 ` John Heffner
2008-07-10 22:15 ` Dan Noe
2008-07-10 21:14 ` Rick Jones [this message]
2008-07-13 18:52 ` Andi Kleen
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=48767BAA.3090704@hp.com \
--to=rick.jones2@hp.com \
--cc=dnoe@limebrokerage.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.