netdev - Re: [PATCH net-next 0/2] RTAX_INITRWND should be able to bring the rcv

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:   Thu, 21 Jul 2022 18:54:01 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Marek Majkowski <marek@...udflare.com>
Cc:     netdev@...r.kernel.org, bpf@...r.kernel.org,
        kernel-team@...udflare.com, ivan@...udflare.com,
        edumazet@...gle.com, davem@...emloft.net, pabeni@...hat.com,
        ast@...nel.org, daniel@...earbox.net, andrii@...nel.org
Subject: Re: [PATCH net-next 0/2] RTAX_INITRWND should be able to bring the
 rcv_ssthresh above 64KiB

On Thu, 21 Jul 2022 17:10:39 +0200 Marek Majkowski wrote:
> Among many route options we support initrwnd/RTAX_INITRWND path
> attribute:
> 
>  $ ip route change local 127.0.0.0/8 dev lo initrwnd 1024
> 
> This sets the initial receive window size (in packets). However, it's
> not very useful in practice. For smaller buffers (<128KiB) it can be
> used to bring the initial receive window down, but it's hard to
> imagine when this is useful. The same effect can be achieved with
> TCP_WINDOW_CLAMP / RTAX_WINDOW option.

I think you based this on bpf-next so you should put bpf-next 
in the subject, it doesn't apply to net-next. Either way let's 
wait for Eric to comment.