netdev - Re: [PATCH] net_sched: sfq: add optional RED on top of SFQ

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1325869679.2911.27.camel@edumazet-laptop>
Date:	Fri, 06 Jan 2012 18:07:59 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Dave Taht <dave.taht@...il.com>
Cc:	David Miller <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>,
	Stephen Hemminger <shemminger@...tta.com>,
	Kathleen Nichols <nichols@...lere.com>,
	Jim Gettys <jg@...edesktop.org>
Subject: Re: [PATCH] net_sched: sfq: add optional RED on top of SFQ

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@...il.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.



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html