From: "Agarwal, Anil" <Anil.Agarwal@viasat.com>
To: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] CoDel Algorithm comments and suggestions
Date: Wed, 17 Jun 2015 00:03:55 +0000 [thread overview]
Message-ID: <7A2801D5E40DD64A85E38DF22117852C70ABFA20@wdc1exchmbxp05.hq.corp.viasat.com> (raw)
In-Reply-To: <7A2801D5E40DD64A85E38DF22117852C70ABF1B9@wdc1exchmbxp05.hq.corp.viasat.com>
Please ignore item #1 in the comments doc - I misread the CoDel spec. Sorry.
Anil
-----Original Message-----
From: codel-bounces@lists.bufferbloat.net [mailto:codel-bounces@lists.bufferbloat.net] On Behalf Of Agarwal, Anil
Sent: Tuesday, June 16, 2015 1:12 PM
To: codel@lists.bufferbloat.net
Subject: [Codel] CoDel Algorithm comments and suggestions
All,
Here are a number of suggestions to improve CoDel algorithm performance, especially under extreme traffic conditions. The suggested changes are in the spirit of the CoDel algorithm and help to make state variable changes more smooth and continuous, rather than abrupt. I confess I have not gone thru all the exchanges on the mailing list, so some items may have been discussed and disposed of before.
Also, see enclosed another document with some simple analysis on the dynamics of CoDel. Nothing earth-shaking, but it was fun and useful to derive the equations.
I have tested the algorithm - with and without the changes - with my own quick implementation of CoDel - with simple unresponsive UDP traffic.
Not tested in ns2 simulations with realistic traffic and various TCP flavors.
Regards,
Anil Agarwal
ViaSat Inc.
prev parent reply other threads:[~2015-06-17 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 17:11 Agarwal, Anil
2015-06-17 0:03 ` Agarwal, Anil [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
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=7A2801D5E40DD64A85E38DF22117852C70ABFA20@wdc1exchmbxp05.hq.corp.viasat.com \
--to=anil.agarwal@viasat.com \
--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