netdev - Re: [PATCH net-next 0/6] mptcp: avoid workqueue usage for data

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]

Message-ID: <20201130183404.01abe8dd@kicinski-fedora-pc1c0hjn.DHCP.thefacebook.com>
Date:   Mon, 30 Nov 2020 18:34:04 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Paolo Abeni <pabeni@...hat.com>
Cc:     netdev@...r.kernel.org, mptcp@...ts.01.org,
        Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH net-next 0/6] mptcp: avoid workqueue usage for data

On Fri, 27 Nov 2020 11:10:21 +0100 Paolo Abeni wrote:
> The current locking schema used to protect the MPTCP data-path
> requires the usage of the MPTCP workqueue to process the incoming
> data, depending on trylock result.
> 
> The above poses scalability limits and introduces random delays
> in MPTCP-level acks.
> 
> With this series we use a single spinlock to protect the MPTCP
> data-path, removing the need for workqueue and delayed ack usage.
> 
> This additionally reduces the number of atomic operations required
> per packet and cleans-up considerably the poll/wake-up code.

Applied, thanks!