CoDel AQM discussions
 help / color / mirror / Atom feed
From: Anirudh Sivaraman <sk.anirudh@gmail.com>
To: codel@lists.bufferbloat.net
Cc: Hari Balakrishnan <hari@csail.mit.edu>,
	Suvinay Subramanian <suvinay@csail.mit.edu>,
	Keith Winstein <keithw@mit.edu>
Subject: [Codel] Work on absence of a universal queue management / scheduling scheme
Date: Tue, 29 Oct 2013 00:04:59 -0400	[thread overview]
Message-ID: <CAMdC6xa8HXRJTF-sccrQs4=4WKHpFtspz0PaH0VxT5-rWG_ZUQ@mail.gmail.com> (raw)

Hello,

I would be grateful for the list's feedback re: our new paper that
attempts to show that there is no universal AQM or scheduling scheme,
and proposes extending SDN to the data plane to allow a switch to
implement different scheduling and queue management algorithms, even
after being installed. The paper, along with instructions to reproduce
its results, is available here:
http://web.mit.edu/anirudh/www/sdn-data-plane.html

We compared three queue-management schemes on a bottleneck gateway in
simulation: CoDel running on a single queue (as described in "man
tc-codel"), CoDel with per-flow queues (fq_codel, as described in "man
tc-fq_codel"), and per-flow queueing with long DropTail queues. It
turns out that depending on the objectives desired by the traffic
running across the gateway, any one of these schemes can be better
than any other -- i.e. A>B>C>A and A>C>B>A. In other words, we don't
think there is likely to be a 'best' AQM scheme

Our proposal to address the absence of a universal in-network
configuration is a switch data plane that's flexible enough to
implement new scheduling and queue management schemes. To be clear,
this work is merely a position paper at this point, and needs a lot
more thought before such a design is feasible at line rates on
switches with an aggregate capacity reaching 1 Terabit/sec. We are
presenting this next month at HotNets, so we are grateful for any
feedback from the list.

Anirudh

                 reply	other threads:[~2013-10-29  4:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAMdC6xa8HXRJTF-sccrQs4=4WKHpFtspz0PaH0VxT5-rWG_ZUQ@mail.gmail.com' \
    --to=sk.anirudh@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=hari@csail.mit.edu \
    --cc=keithw@mit.edu \
    --cc=suvinay@csail.mit.edu \
    /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