General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "David Täht" <dave.taht@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] the observed sack oddity
Date: Tue, 11 Oct 2011 15:33:33 +0200	[thread overview]
Message-ID: <1318340013.2538.30.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <4E94408A.4030709@gmail.com>

Le mardi 11 octobre 2011 à 15:11 +0200, David Täht a écrit :
> Of course, it would help if I posted a link to the screenshots!
> 
> http://www.teklibre.com/~d/sackoddity/
> 
> On 10/11/2011 03:09 PM, David Täht wrote:
> > I have put up screenshots of tcptrace -G and xplot.org's analysis of my
> > most recent capture of an ipv6 connection over freebox (wired) from a
> > debloat-testing kernel here in france (pre 3.1 by a lot) to a 2.6.16
> > kernel (the aformentioned netsonar box) in redwood city, ca, both
> > running tcp cubic, over ipv6.
> >
> > at first glance, it looked a lot like a classic bufferbloat trace, with
> > complete with periodic collapses and cubic increasing the window.
> >
> > Then I noticed the sacks.
> >
> > I also have a trace taken between the debloat-testing box and a cerowrt
> > box (running linux 3.04), both running westwood, which shows
> > considerably less undesirable behavior, and I will repeat that test with
> > cubic this evening and post additional data tomorrow morning.


Who is the sender ?

Is some WIFI involved ?

"netstat -s" on the receiver would help

This might be a truesize mismatch.




  reply	other threads:[~2011-10-11 13:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 10:27 [Bloat] a flood of Bufferbloat-related papers David Täht
2011-10-11 11:58 ` Steinar H. Gunderson
2011-10-11 12:13   ` Eric Dumazet
2011-10-11 12:18     ` Eric Dumazet
2011-10-11 13:09       ` [Bloat] the observed sack oddity David Täht
2011-10-11 13:11         ` David Täht
2011-10-11 13:33           ` Eric Dumazet [this message]
2011-10-11 13:51             ` David Täht
2011-10-11 15:25         ` Justin McCann
2011-10-11 15:37         ` Justin McCann
2011-10-13 18:23         ` Jan Ceuleers
2011-10-13 18:27           ` Eric Dumazet
2011-10-11 12:40     ` [Bloat] a flood of Bufferbloat-related papers David Täht
2011-10-11 12:17   ` David Täht
2011-10-12  7:49 ` Lawrence Stewart
2011-10-12  8:03   ` David Täht

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1318340013.2538.30.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
    --to=eric.dumazet@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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