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: <CAADnVQKWSmjcy727_mhZvMnO=TdAjpA_0=LfABd9FwYUzZuW7Q@mail.gmail.com>
Date:   Mon, 24 Aug 2020 14:43:18 -0700
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Martin KaFai Lau <kafai@...com>
Cc:     bpf <bpf@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Kernel Team <kernel-team@...com>,
        Lawrence Brakmo <brakmo@...com>,
        Neal Cardwell <ncardwell@...gle.com>,
        Network Development <netdev@...r.kernel.org>,
        Yuchung Cheng <ycheng@...gle.com>
Subject: Re: [PATCH v5 bpf-next 00/12] BPF TCP header options

On Thu, Aug 20, 2020 at 12:00 PM Martin KaFai Lau <kafai@...com> wrote:
>
> The earlier effort in BPF-TCP-CC allows the TCP Congestion Control
> algorithm to be written in BPF.  It opens up opportunities to allow
> a faster turnaround time in testing/releasing new congestion control
> ideas to production environment.
>
> The same flexibility can be extended to writing TCP header option.
> It is not uncommon that people want to test new TCP header option
> to improve the TCP performance.  Another use case is for data-center
> that has a more controlled environment and has more flexibility in
> putting header options for internal traffic only.
>
> This patch set introduces the necessary BPF logic and API to
> allow bpf program to write and parse header options.
>
> There are also some changes to TCP and they are mostly to provide
> the needed sk and skb info to the bpf program to make decision.
>
> Patch 9 is the main patch and has more details on the API and design.
>
> The set includes an example which sends the max delay ack in
> the BPF TCP header option and the receiving side can
> then adjust its RTO accordingly.
>
> v5:
> - Move some of the comments from git commit message to the UAPI bpf.h
>   in patch 9
>
> - Some variable clean up in the tests (patch 11).

Applied. Thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ