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: <dfa31033-c4c1-4430-81b2-5df41afc33a2@gmail.com>
Date: Fri, 17 Jan 2025 16:19:09 +0000
From: Pavel Begunkov <asml.silence@...il.com>
To: Paolo Abeni <pabeni@...hat.com>, Jakub Kicinski <kuba@...nel.org>
Cc: Jens Axboe <axboe@...nel.dk>, "David S. Miller" <davem@...emloft.net>,
 Eric Dumazet <edumazet@...gle.com>, Jesper Dangaard Brouer
 <hawk@...nel.org>, David Ahern <dsahern@...nel.org>,
 Mina Almasry <almasrymina@...gle.com>,
 Stanislav Fomichev <stfomichev@...il.com>, Joe Damato <jdamato@...tly.com>,
 Pedro Tammela <pctammela@...atatu.com>, David Wei <dw@...idwei.uk>,
 io-uring@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v11 00/21] io_uring zero copy rx

On 1/17/25 16:05, Paolo Abeni wrote:
> On 1/17/25 3:42 PM, Pavel Begunkov wrote:
>> On 1/17/25 14:28, Paolo Abeni wrote:
>>> On 1/17/25 12:16 AM, David Wei wrote:
>>>> This patchset adds support for zero copy rx into userspace pages using
>>>> io_uring, eliminating a kernel to user copy.
>>>>
...
>>>> Broadcom bnxt support:
>>>> [1]: https://lore.kernel.org/netdev/20241003160620.1521626-8-ap420073@gmail.com/
>>>>
>>>> Linux kernel branch:
>>>> [2]: https://github.com/spikeh/linux.git zcrx/v9
>>>>
>>>> liburing for testing:
>>>> [3]: https://github.com/isilence/liburing.git zcrx/next
>>>>
>>>> kperf for testing:
>>>> [4]: https://git.kernel.dk/kperf.git
>>>
>>> We are getting very close to the merge window. In order to get this
>>> series merged before such deadline the point raised by Jakub on this
>>> version must me resolved, the next iteration should land to the ML
>>> before the end of the current working day and the series must apply
>>> cleanly to net-next, so that it can be processed by our CI.
>>
>> Sounds good, thanks Paolo.
>>
>> Since the merging is not trivial, I'll send a PR for the net/
>> patches instead of reposting the entire thing, if that sounds right
>> to you. The rest will be handled on the io_uring side.
> 
> I agree it is the more straight-forward path. @Jakub: do you see any
> problem with the above?

I couldn't cleanly base it onto linus' branch, so after talking it
over with Jens, I sent it as a normal patchset. Jens will help to
handle the rest if the net patches are merged.

-- 
Pavel Begunkov


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ