From: Andi Kleen <andi@firstfloor.org>
To: "Dan Noé" <dnoe@limebrokerage.com>
Cc: netdev@vger.kernel.org
Subject: Re: Detecting TCP loss on the receiving side?
Date: Sun, 13 Jul 2008 20:52:48 +0200 [thread overview]
Message-ID: <87iqv9zke7.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4876668C.8040108@limebrokerage.com> (Dan Noé's message of "Thu, 10 Jul 2008 15:44:12 -0400")
Dan Noé <dnoe@limebrokerage.com> writes:
> We're trying to troubleshoot some problems and we'd like to use the
> struct tcp_info method to gain some information and attempt to detect
> TCP loss events on the receiving side of a TCP stream.
Receiver Loss can be diagnosed using netstat -s at least. Especially if you
can rule out reordering. But only system global currently, although
that might change with containers.
-Andi
prev parent reply other threads:[~2008-07-13 18:52 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
2008-07-13 18:52 ` Andi Kleen [this message]
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=87iqv9zke7.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--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 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).