General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Simon Barber <simon@superduper.net>
Cc: bloat <bloat@lists.bufferbloat.net>,
	Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [Bloat] AQM and PPP on Linux
Date: Tue, 28 Jul 2015 16:55:19 +0200	[thread overview]
Message-ID: <1438095319.20182.56.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <1438094970.20182.53.camel@edumazet-glaptop2.roam.corp.google.com>

On Tue, 2015-07-28 at 16:49 +0200, Eric Dumazet wrote:
> On Tue, 2015-07-28 at 07:31 -0700, Simon Barber wrote:
> > The issue is that Codel tries to keep the delay low, and will start 
> > dropping when sojourn time grows above 5ms for 100ms. For longer RTT links 
> > more delay is necessary to avoid underutilizing the link. This is due to 
> > the multiplicative decrease - it's worst with Reno, where the halving of 
> > cWind means that you need to have a full BDP of data in the buffer to avoid 
> > the link going idle when cWind is halved. With longer RTTs this means more 
> > delay than Codel allows is required to avoid a throughput hit. The worst 
> > case happens when a single flow is controlled, but that can be a common 
> > situation. My proposal is to sense and have the target value in Codel 
> > automatically adjust when this worst case scenario happens - which would 
> > mitigate most of the downside.
> 
> As I said, I've never seen what you describe.
> 
> 100ms value is not a go/nogo threshold. It is a hint, based on real
> world values. We are speaking of 100 ms sojourn time in the CoDel queue,

typo : 5 ms ( codel target )



  reply	other threads:[~2015-07-28 14:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 13:09 Juliusz Chroboczek
2015-07-28 13:33 ` Toke Høiland-Jørgensen
2015-07-28 13:50   ` Juliusz Chroboczek
2015-07-28 14:05     ` Toke Høiland-Jørgensen
2015-07-28 14:11       ` Simon Barber
2015-07-28 14:21         ` Eric Dumazet
2015-07-28 14:31           ` Simon Barber
2015-07-28 14:43             ` Jonathan Morton
2015-07-28 14:49             ` Eric Dumazet
2015-07-28 14:55               ` Eric Dumazet [this message]
2015-07-28 16:02               ` Alan Jenkins
2015-07-28 16:22             ` Sebastian Moeller
2015-07-28 17:11               ` Michael Welzl
2015-07-29  7:19         ` David Lang
2015-07-28 19:20       ` Juliusz Chroboczek
2015-07-28 19:29         ` Alan Jenkins
2015-07-28 14:18     ` Eric Dumazet
2015-07-28 14:44 ` Dave Taht
2015-07-28 14:52   ` Eric Dumazet
2015-07-28 19:24   ` Juliusz Chroboczek
2015-07-28 19:31     ` Bill Ver Steeg (versteb)
2015-07-28 20:10     ` Alan Jenkins
2015-07-28 20:45       ` Alan Jenkins
2015-07-29 13:15   ` Stefan Alfredsson
2015-07-29 13:41     ` Dave Taht

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=1438095319.20182.56.camel@edumazet-glaptop2.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jch@pps.univ-paris-diderot.fr \
    --cc=simon@superduper.net \
    /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