From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Stephen Hemminger <shemminger@vyatta.com>,
Kathleen Nichols <nichols@pollere.com>,
Jim Gettys <jg@freedesktop.org>
Subject: Re: [PATCH] net_sched: sfq: add optional RED on top of SFQ
Date: Fri, 06 Jan 2012 18:07:59 +0100 [thread overview]
Message-ID: <1325869679.2911.27.camel@edumazet-laptop> (raw)
In-Reply-To: <CAA93jw7024Ejncj_Gjg9jcQF=HTERkc0dSCrVKrv7XJfELryow@mail.gmail.com>
Le vendredi 06 janvier 2012 à 17:56 +0100, Dave Taht a écrit :
> On Fri, Jan 6, 2012 at 5:31 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> > Adds an optional Random Early Detection on each SFQ flow queue.
>
> netperf -t TCP_RR is useful
> -t TCP_MAERTS will be interesting.
> simultaneous ping?
>
I dont know what you expect from pings, since they are already coming in
new flows (unless a ping flood is in effect), so RED doesnt fire for
these packets.
Same for TCP_RR : Since at most one packet is in flight per flow, RED
cannot fire.
So there is no differences for them.
next prev parent reply other threads:[~2012-01-06 17:08 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 [this message]
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
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=1325869679.2911.27.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=jg@freedesktop.org \
--cc=netdev@vger.kernel.org \
--cc=nichols@pollere.com \
--cc=shemminger@vyatta.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