From: Stephen Hemminger <shemminger@vyatta.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [PATCH] net_sched: sfq: add optional RED on top of SFQ
Date: Fri, 6 Jan 2012 09:09:29 -0800 [thread overview]
Message-ID: <20120106090929.009a78d6@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1325867504.2911.23.camel@edumazet-laptop>
On Fri, 06 Jan 2012 17:31:44 +0100
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Adds an optional Random Early Detection on each SFQ flow queue.
>
> Traditional SFQ limits count of packets, while RED permits to also
> control number of bytes per flow, and adds ECN capability as well.
>
> 1) We dont handle the idle time management in this RED implementation,
> since each 'new flow' begins with a null qavg. We really want to address
> backlogged flows.
>
> 2) if headdrop is selected, we try to ecn mark first packet instead of
> currently enqueued packet. This gives faster feedback for tcp flows
> compared to traditional RED [ marking the last packet in queue ]
>
> Example of use :
>
> tc qdisc add dev $DEV parent 1:1 handle 10: est 1sec 4sec sfq \
> limit 3000 headdrop flows 512 divisor 16384 \
> redflowlimit 100000 min 8000 max 60000 probability 0.20 ecn
>
> qdisc sfq 10: parent 1:1 limit 3000p quantum 1514b depth 127 headdrop
> flows 512/16384 divisor 16384
> ewma 6 min 8000b max 60000b probability 0.2 ecn
> prob_mark 0 prob_mark_head 4876 prob_drop 6131
> forced_mark 0 forced_mark_head 0 forced_drop 0
> Sent 1175211782 bytes 777537 pkt (dropped 6131, overlimits 11007
> requeues 0)
> rate 99483Kbit 8219pps backlog 689392b 456p requeues 0
>
> In this test, with 64 netperf TCP_STREAM sessions, 50% using ECN enabled
> flows, we can see number of packets CE marked is smaller than number of
> drops (for non ECN flows)
>
> If same test is run, without RED, we can check backlog is much bigger.
>
> qdisc sfq 10: parent 1:1 limit 3000p quantum 1514b depth 127 headdrop
> flows 512/16384 divisor 16384
> Sent 1148683617 bytes 795006 pkt (dropped 0, overlimits 0 requeues 0)
> rate 98429Kbit 8521pps backlog 1221290b 841p requeues 0
>
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
> CC: Stephen Hemminger <shemminger@vyatta.com>
> CC: Dave Taht <dave.taht@gmail.com>
Since SFQ is classful, I don't see what this buys over just putting
a red qdisc under each SFQ class?
next prev parent reply other threads:[~2012-01-06 17:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 12:25 [PATCH net-next] net_sched: red: split red_parms into parms and vars Eric Dumazet
2012-01-05 13:03 ` Dave Taht
2012-01-05 13:39 ` Eric Dumazet
2012-01-06 5:47 ` Eric Dumazet
2012-01-06 8:31 ` Dave Taht
2012-01-06 16:31 ` [PATCH] net_sched: sfq: add optional RED on top of SFQ Eric Dumazet
2012-01-06 16:56 ` Dave Taht
2012-01-06 17:07 ` Eric Dumazet
2012-01-06 17:36 ` Dave Taht
2012-01-06 18:30 ` Rick Jones
2012-01-06 19:33 ` Eric Dumazet
2012-01-06 19:43 ` Rick Jones
2012-01-06 20:26 ` Dave Taht
2012-01-06 17:09 ` Stephen Hemminger [this message]
2012-01-06 17:25 ` Eric Dumazet
2012-01-10 9:40 ` Dave Taht
2012-01-13 4:06 ` David Miller
2012-01-05 19:08 ` [PATCH net-next] net_sched: red: split red_parms into parms and vars David Miller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120106090929.009a78d6@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.