Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: Yuchung Cheng <ycheng@google.com>
Cc: Hsiao-keng Jerry Chu <hkchu@google.com>,
	bloat-devel@lists.bufferbloat.net
Subject: Re: tcp fast open?
Date: Mon, 20 Feb 2012 23:55:45 +0100	[thread overview]
Message-ID: <7i39a515e6.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <CAK6E8=cmr8jH+VX+HGiaDCQxMZVFofFEY_dXt9m6-bzc_Z1Gdw@mail.gmail.com> (Yuchung Cheng's message of "Fri, 17 Feb 2012 07:24:32 -0800")

> Btw, I am very interested in learning the result of AQM vs
> delayed-based CC like ledbat.

That's something that I discussed with the creators of LEDBAT a year ago
(when they convinced me to implement µTP in Transmission).  Here's what
I recall of what Shalunov told me -- but it was a long time ago, and
I was badly jetlagged, so I could be speaking nonsense.

LEDBAT reacts to loss in exactly the same way as Reno does -- it reduces
its congestion window by 1/2.  Hence, if the bottleneck is running an
agressive loss-based AQM such as BLUE, then LEDBAT will behave just the
same as NewReno.

Note that this is not the case of the variant of LEDBAT implemented in
µTP, which on loss divides its window by 1/sqrt(2) (if memory serves).
Hence, µTP will, in that case, behave like an aggregate of two Reno
flows.  However, since µTP doesn't implement slow start or fast
recovery, µTP should still end up being far less agressive than Reno.

--jch

      parent reply	other threads:[~2012-02-20 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-17 14:38 Dave Taht
2012-02-17 15:24 ` Yuchung Cheng
2012-02-20 21:40   ` Dan McDonald
2012-02-21  7:30     ` Jerry Chu
2012-02-21 18:25     ` Rick Jones
2012-02-23 18:20       ` Justin McCann
2012-02-20 22:55   ` Juliusz Chroboczek [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=7i39a515e6.fsf@lanthane.pps.jussieu.fr \
    --to=jch@pps.jussieu.fr \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=hkchu@google.com \
    --cc=ycheng@google.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