netdev - Re: [PATCH net-next v13 00/10] io

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] [day] [month] [year] [list]

Message-ID: <7cdf38e2-640d-4399-974f-fb27183ebe47@gmail.com>
Date: Wed, 5 Feb 2025 19:04:05 +0000
From: Pavel Begunkov <asml.silence@...il.com>
To: David Ahern <dsahern@...nel.org>, David Wei <dw@...idwei.uk>,
 netdev@...r.kernel.org
Cc: Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Jesper Dangaard Brouer <hawk@...nel.org>,
 Mina Almasry <almasrymina@...gle.com>,
 Stanislav Fomichev <stfomichev@...il.com>, Joe Damato <jdamato@...tly.com>,
 Pedro Tammela <pctammela@...atatu.com>
Subject: Re: [PATCH net-next v13 00/10] io_uring zero copy rx

On 2/5/25 18:43, David Ahern wrote:
> On 2/5/25 11:00 AM, David Wei wrote:
>> On 2025-02-05 09:44, David Ahern wrote:
>>> On 2/4/25 2:56 PM, David Wei wrote:
>>>> We share netdev core infra with devmem TCP. The main difference is that
>>>> io_uring is used for the uAPI and the lifetime of all objects are bound
>>>> to an io_uring instance. Data is 'read' using a new io_uring request
>>>> type. When done, data is returned via a new shared refill queue. A zero
>>>> copy page pool refills a hw rx queue from this refill queue directly. Of
>>>> course, the lifetime of these data buffers are managed by io_uring
>>>> rather than the networking stack, with different refcounting rules.
>>>
>>> just to make sure I understand, working with GPU memory as well as host
>>> memory is not a goal of this patch set?
>>
>> Yes, this patchset is only for host memory.
> 
> And is GPU memory on the near term to-do list?

Not a priority, but yes, and it's fairly easy to add as it'd
only need changes in setup disregard the fallback path.

-- 
Pavel Begunkov