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]

Date:	Fri, 06 Jan 2012 18:25:59 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Stephen Hemminger <shemminger@...tta.com>
Cc:	David Miller <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>, Dave Taht <dave.taht@...il.com>
Subject: Re: [PATCH] net_sched: sfq: add optional RED on top of SFQ

Le vendredi 06 janvier 2012 à 09:09 -0800, Stephen Hemminger a écrit :

> Since SFQ is classful, I don't see what this buys over just putting
> a red qdisc under each SFQ class?
> 

You meant RED is classful, not SFQ ?

Idea is to use RED on each flow, not on global SFQ, since as you pointed
out, you already can do that right now (and it has no interest)

You can have this right now using QFQ, and for each QFQ class, attach a
RED qdisc, but memory cost and setup time are crazy.

Please note that RED cant perform head mark or drop. (unless we add new
qdisc ops for this)
We can do it from SFQ because we do our proper queue management.



--
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