From: Simon Barber <simon@superduper.net>
To: codel@lists.bufferbloat.net
Subject: [Codel] sawtooth
Date: Wed, 27 Mar 2013 16:34:03 -0700 [thread overview]
Message-ID: <515381EB.8030709@superduper.net> (raw)
I've been thinking about codel's behaviour with a single TCP stream. TCP
in steady state exhibits a sawtooth cwin behaviour. cwind rises by 1
each RTT until the queue drops a packet, then cwind halves, and repeat.
With codel the earliest a packet will be dropped is 100ms after the
queue size grows to the point the sojourn is 5ms. At this point the cwin
is halved. For small RTTs or with multiple flows this may ensure good
utilisation, but for large RTTs and a single flow surely dropping this
early could result in starvation?
Simon
next reply other threads:[~2013-03-27 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 23:34 Simon Barber [this message]
2013-03-28 16:10 ` 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=515381EB.8030709@superduper.net \
--to=simon@superduper.net \
--cc=codel@lists.bufferbloat.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