netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: John Heffner <johnwheffner@gmail.com>
Cc: "Dan Noé" <dnoe@limebrokerage.com>, netdev@vger.kernel.org
Subject: Re: Detecting TCP loss on the receiving side?
Date: Thu, 10 Jul 2008 14:20:07 -0700	[thread overview]
Message-ID: <48767D07.2000003@hp.com> (raw)
In-Reply-To: <1e41a3230807101405y437dff4er443185be3228caa5@mail.gmail.com>

John Heffner wrote:
> Looking for loss at the receiver is a bit tricky.  It doesn't look
> like struct tcp_info has enough information to do this easily.  If you
> are able to install a custom kernel on this machine, the Web100 patch
> would be able to gather enough information to figure it out.  The
> basic idea would be to look for a difference between RcvNxt and
> RcvMax.

And even then it depends on the connections having multiple segments in 
flight at one time.  Although I suppose that cuts both ways and affects 
the tracing too, but perhaps not to the same extent.

Dan - seeing "brokerage" in your email and worries about latency makes 
me think that your app(s) are pushing around lots of small messages - 
are those spread-out across lots of connections, or are they 
consolidated into a rather smaller number of connections?  Also, what is 
the magnitude of the latency in these latency events?

rick jones

  reply	other threads:[~2008-07-10 21:20 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 [this message]
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

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=48767D07.2000003@hp.com \
    --to=rick.jones2@hp.com \
    --cc=dnoe@limebrokerage.com \
    --cc=johnwheffner@gmail.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).