[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da6b478a-065a-4f02-acd2-03c6d6dea9fa@davidwei.uk>
Date: Wed, 5 Feb 2025 10:00:13 -0800
From: David Wei <dw@...idwei.uk>
To: David Ahern <dsahern@...nel.org>, netdev@...r.kernel.org
Cc: Pavel Begunkov <asml.silence@...il.com>, 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 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.
Powered by blists - more mailing lists