CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Simon Barber <simon@superduper.net>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] Worst case conditions - large RTT
Date: Wed, 9 May 2012 13:41:04 -0700	[thread overview]
Message-ID: <CAA93jw6vogSQFenNVN3PQqDauC2iRavCLzWZPZAtWemszbZscw@mail.gmail.com> (raw)
In-Reply-To: <4FAAD534.2030100@superduper.net>

On Wed, May 9, 2012 at 1:36 PM, Simon Barber <simon@superduper.net> wrote:
> Codel assesses the minimum delay over a fixed time period (the interval) -
> what happens when the interval is much smaller that the RTT. For example a
> tcp stream is experiencing a 2 second RTT (perhaps due to bufferbloat at
> some point), yet the interval is 100ms. The TCP implementation is a poor one
> that will ACK a window at a time. Here codel will drop excessively, and
> cause low throughput?
>

You are doing a great job of asking good questions.

I would hope we could get some more people lined up to answer them,
armed with sims and real hardware. Volunteers for each problem would
be helpful.

Me, I'd like very much to get some data back on the variable bandwidth
wireless scenario! Except that cerowrt's too broken at the moment to
use and I'm trying to fix that.

The latest netem does ECN, btw. And ns3 has a decent minstrel model.
(hint, hint)

> Simon
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel



-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

  reply	other threads:[~2012-05-09 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 20:36 Simon Barber
2012-05-09 20:41 ` Dave Taht [this message]
2012-05-09 21:08   ` Jim Gettys
2012-05-09 20:42 ` Kathleen Nichols

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/codel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw6vogSQFenNVN3PQqDauC2iRavCLzWZPZAtWemszbZscw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --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