CoDel AQM discussions
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: codel@lists.bufferbloat.net, Jesper Dangaard Brouer <jbrouer@redhat.com>
Subject: Re: [Codel] hardware multiqueue in fq_codel?
Date: Fri, 12 Jul 2013 13:35:47 -0400	[thread overview]
Message-ID: <CAA93jw6JM-SQsRUCJjQPEy=+iQ02Px2UJmvN9nUH-ZLLeizBHA@mail.gmail.com> (raw)
In-Reply-To: <1373649589.10804.34.camel@edumazet-glaptop>

On Fri, Jul 12, 2013 at 1:19 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Fri, 2013-07-12 at 12:54 -0400, Dave Taht wrote:
>
>> My point was that same program would be just as damaging against
>> pfifo_fast.
>>
>> > Or just think of SYN flood attack.
>>
>> For which other defenses exist.
>
> If someone uses pfifo_fast, it needs no particular protection right now
> to be able to log in into his machine.

Against a syn flood attack?

> Thats the point you absolutely missed. Its kind of incredible.

I guess I'm still entirely missing it. By default the networks I have
are protected by the syn_flood mechanism as enabled in openwrt.

I have hit them with attack tools like thc and related stuff, and well,
that list is rather incredibly large but not bound to the queue type
and I'd rather discuss it offlist.

So if you can point me at some code that thoroughly disables
fq_codel worse than pfifo_fast (offlist), I'll gladly run it on
the testbed here, against everything:

http://results.lab.taht.net/

One of the big reasons why I haven't advocated a smaller number
of flows by default in fq_codel was due to the attack protection I
surmised it + the permuted hash - provided.

> If fq_codel could replace pfifo_fast as is, why do you think I did not
> submit the patch doing the change ????

I have generally always thought a three tier system was still
needed, just far less so. The characteristics of that system
are what we are discussing now. The time spent analyzing
fq_codel's behavior


>
>
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2013-07-12 17:35 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
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 [this message]
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='CAA93jw6JM-SQsRUCJjQPEy=+iQ02Px2UJmvN9nUH-ZLLeizBHA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=eric.dumazet@gmail.com \
    --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