CoDel AQM discussions
 help / color / mirror / Atom feed
From: James Roberts <James.Roberts@inria.fr>
To: codel@lists.bufferbloat.net
Subject: [Codel] FQ_Codel v. FQ_LQD
Date: Tue, 12 Feb 2013 10:29:45 +0100	[thread overview]
Message-ID: <88264AA4-1200-4078-8A94-41D814899C8F@inria.fr> (raw)

I have not been following Bufferbloat but a colleague forwarded to me the latest post from Dave Täht about FQ_Codel. It is good to see the virtues of fair queuing are being rediscovered. 

I think the work by Suter and co-authors on FQ in high capacity routers is particularly relevant:

B. Suter, T. Lakshman, D. Stiliadis, A. Choudhury, Buffer Management Schemes
for Supporting TCP in Gigabit Routers with Per-Flow Queuing, IEEE Journal in
Selected Areas un Communications, August 1999. (http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=772451)

They may have been the first to introduce "head drop". Actually they advocated dropping from the front of the flow queue with longest backlog (FQ_LQD). I am not sure why a more sophisticated AQM, like RED, ARED or Codel, is better than longest queue drop.

Another advantage of FQ_Codel highlighted in the report by Toke Høiland-Jørgensen (notified on the list) is to give priority to packets of newly active flows. This idea was already proposed in our papers:

A. Kortebi, S. Oueslati and J. Roberts. Cross-protect: implicit service differentiation and admission control,  IEEE HPSR 2004, Phoenix, USA, April 2004. 
A. Kortebi, S. Oueslati, J. Roberts. Implicit service differentiation using Deficit Round Robin,  Proceedings of ITC 19, Beijing, August 2005. 

I have long been advocating per flow fairness as the basis of effective traffic control so I hope you won't mind me recalling this prior work.

Jim Roberts

             reply	other threads:[~2013-02-12  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12  9:29 James Roberts [this message]
2013-02-12 15:01 ` Dave Taht

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=88264AA4-1200-4078-8A94-41D814899C8F@inria.fr \
    --to=james.roberts@inria.fr \
    --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