netdev - Re: [PATCH iproute2-next] tc: red: allow setting th_min and th

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] [day] [month] [year] [list]

Message-ID: <78b62f7d-21be-d6c8-06ef-ae2200a75afa@gmail.com>
Date:   Fri, 19 Jan 2018 12:37:19 -0800
From:   David Ahern <dsahern@...il.com>
To:     Jakub Kicinski <jakub.kicinski@...ronome.com>,
        stephen@...workplumber.org
Cc:     netdev@...r.kernel.org, oss-drivers@...ronome.com
Subject: Re: [PATCH iproute2-next] tc: red: allow setting th_min and th_max to
 the same value

On 1/16/18 3:08 PM, Jakub Kicinski wrote:
> Setting th_min and th_max to the same value may be useful for DCTCP
> deployments.  The original DCTCP paper describes it as a simplest way
> of achieving simple ECN threshold marking.  Indeed, there doesn't seem
> to be any simpler qdisc in Linux which would allow such a setup today.
> 
> Signed-off-by: Jakub Kicinski <jakub.kicinski@...ronome.com>
> Reviewed-by: Dirk van der Merwe <dirk.vandermerwe@...ronome.com>
> ---
> Or should I go ahead and add a DCTCP qdisc? :)
> 
>  tc/tc_red.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 

applied to iproute2-next