CoDel AQM discussions
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] hardware multiqueue in fq_codel?
Date: Fri, 12 Jul 2013 08:13:21 -0700	[thread overview]
Message-ID: <1373642001.10804.18.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130712113413.4b601800@redhat.com>

On Fri, 2013-07-12 at 11:34 +0200, Jesper Dangaard Brouer wrote:

> I also think of "fq_codel" as a good replacement for pfifo_fast.  As
> the 3-PRIO bands in pfifo_fast is replaced with something smarter in
> "fq_codel". (IMHO please don't try to add a prio_fq_codel, just be because
> pfifo_fast had prio bands, people can just enable a prio qdisc if they
> really need it).

Nope. Its really easy for an attacker to flood your fq_codel with say
UDP messages on all available hash slots.

Some people really want the high prio packets to be sent before any
med/low prio packets. Not everybody uses a separate ethernet port for
management and heartbeats.

If we want to replace pfifo_fast as the default qdisc, we want some
integrated qdisc with 3 bands.

I presume something really simple like :

a fifo for band 0 messages
a fq_codel for band 1 messages
a fifo for band 2 messages

Would be more than enough, and this also should use device txqueue len
as the (dynamic) limit, because some existing scripts expect to control
qdisc limit using "ifconfig eth0 txqueuelen 100", not a tc script.




  reply	other threads:[~2013-07-12 15:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 17:09 Dave Taht
2013-07-11 17:44 ` Eric Dumazet
2013-07-11 18:06   ` Dave Taht
2013-07-11 18:54     ` Eric Dumazet
2013-07-11 21:18       ` Dave Taht
2013-07-12  0:06         ` Eric Dumazet
2013-07-12  0:48           ` Dave Taht
2013-07-12  9:34         ` Jesper Dangaard Brouer
2013-07-12 15:13           ` Eric Dumazet [this message]
2013-07-12 16:36             ` Sebastian Moeller
2013-07-12 16:54               ` Eric Dumazet
2013-07-12 17:00                 ` Dave Taht
2013-07-15 13:40                 ` Jesper Dangaard Brouer
2013-07-15 13:57                   ` Eric Dumazet
2013-07-15 14:24                     ` Jesper Dangaard Brouer
2013-07-15 15:30                     ` Eric Dumazet
2013-07-15 17:19                     ` Dave Taht
2013-07-12 16:37             ` Dave Taht
2013-07-12 16:39               ` Dave Taht
2013-07-12 16:50               ` Eric Dumazet
2013-07-12 16:54                 ` Dave Taht
2013-07-12 17:19                   ` Eric Dumazet
2013-07-12 17:35                     ` Dave Taht
2013-07-12 17:47                       ` Eric Dumazet
2013-07-12 18:06                         ` Dave Taht
2013-07-15 12:56                     ` Jesper Dangaard Brouer
2013-07-12 17:32                   ` luca.muscariello
2013-07-11 19:41     ` Jonathan Morton

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=1373642001.10804.18.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=jbrouer@redhat.com \
    /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