netdev - Re: [PATCH net-next] tcp: tsq: no longer use limit_output

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 for Android: free password hash cracker in your pocket

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

Date:   Sun, 11 Nov 2018 13:57:33 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     edumazet@...gle.com
Cc:     netdev@...r.kernel.org, eric.dumazet@...il.com
Subject: Re: [PATCH net-next] tcp: tsq: no longer use limit_output_bytes
 for paced flows

From: Eric Dumazet <edumazet@...gle.com>
Date: Sun, 11 Nov 2018 07:34:28 -0800

> FQ pacing guarantees that paced packets queued by one flow do not
> add head-of-line blocking for other flows.
> 
> After TCP GSO conversion, increasing limit_output_bytes to 1 MB is safe,
> since this maps to 16 skbs at most in qdisc or device queues.
> (or slightly more if some drivers lower {gso_max_segs|size})
> 
> We still can queue at most 1 ms worth of traffic (this can be scaled
> by wifi drivers if they need to)
> 
> Tested:
 ...
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>

Applied.