CoDel AQM discussions
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Wes Felter <wmf@felter.org>,
	codel@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net,
	bloat@lists.bufferbloat.net
Subject: Re: [Codel] [Bloat] Latest codel, fq_codel, and pie sim study from cablelabs now available
Date: Wed, 08 May 2013 15:54:57 -0700	[thread overview]
Message-ID: <1368053697.13473.28.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAA93jw6GMMCcR4HvR1632bT4p9XFEAG=zFx4iuUVASL8k5GU5A@mail.gmail.com>

On Wed, 2013-05-08 at 15:25 -0700, Dave Taht wrote:


> Heh. I am hoping you are providing this as a negative proof!? as the
> strict prioritization of this particular linux scheduler means that a
> single full rate TCP flow in class 1:1 will completely starve classes
> 1:2 and 1:3.
> 
> Some level of fairness between service classes is needed too. My most
> common setting for the "cake" shaper has been 20% minimum for the
> background traffic, for example. I am unsure if codel is really the
> right thing for the highest priority qdisc, as everything
> 

PRIO qdisc does strict priority, like pfifo_fast.

If your high prio traffic is also using 100% of the bandwith, then there
is a fundamental problem about classifying this so called high prio
traffic.

On my hosts, high prio traffic uses less than 0.1 % of the bandwidth,
so I do not need to have DRR kind of setup.

And the low priority traffic has no minimum guaranteed bandwidth.

There is no 'magic solution' for every needs. The solution I gave is
good enough if you need to have some strict priorities, as a replacement
to current pfifo_fast, and if all traffic is not miss classified.

A setup using DRR instead of PRIO is also possible.



  reply	other threads:[~2013-05-08 22:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 11:23 [Codel] " Dave Taht
2013-05-01 20:26 ` [Codel] [Bloat] " Simon Barber
2013-05-02  0:00   ` Jonathan Morton
2013-05-02  2:20     ` Simon Barber
2013-05-02  4:59       ` Andrew McGregor
2013-05-02 12:04       ` Jonathan Morton
2013-05-02 13:29         ` Simon Perreault
2013-05-14  2:26         ` Dan Siemon
2013-05-14  4:56           ` Tristan Seligmann
2013-05-14 10:24             ` Dave Taht
2013-05-14 13:02               ` Eric Dumazet
2013-06-11 18:19             ` [Codel] [Cerowrt-devel] " Michael Richardson
2013-05-14 12:12           ` [Codel] " Jesper Dangaard Brouer
2013-05-06 17:54       ` Jesper Dangaard Brouer
2013-05-06 18:46         ` Jonathan Morton
2013-05-06 20:47           ` Jesper Dangaard Brouer
2013-05-07 16:22             ` Greg White
2013-05-07 13:31       ` [Codel] [Cerowrt-devel] " Michael Richardson
2013-05-07 16:30         ` [Codel] [Bloat] [Cerowrt-devel] " Greg White
2013-05-07 19:56           ` [Codel] [Bloat] " Wes Felter
2013-05-07 20:30             ` Eric Dumazet
2013-05-08 22:25               ` Dave Taht
2013-05-08 22:54                 ` Eric Dumazet [this message]
2013-05-09  1:45                   ` Andrew McGregor

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=1368053697.13473.28.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=wmf@felter.org \
    /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