On 10/28/24 12:11, Christoph Hellwig wrote:
On Thu, Oct 24, 2024 at 05:40:02PM +0100, Pavel Begunkov wrote:
On 10/24/24 17:06, Christoph Hellwig wrote:
On Thu, Oct 24, 2024 at 03:23:06PM +0100, Pavel Begunkov wrote:
That's not what this series does. It adds the new memory_provider_ops
set of
On 10/24/24 17:06, Christoph Hellwig wrote:
On Thu, Oct 24, 2024 at 03:23:06PM +0100, Pavel Begunkov wrote:
That's not what this series does. It adds the new memory_provider_ops
set of hooks, with once implementation for dmabufs, and one for
io_uring zero copy.
First, it's not a _new_ abstrac
On 10/24/24 10:23, Christoph Hellwig wrote:
On Wed, Oct 23, 2024 at 03:34:53PM +0100, Pavel Begunkov wrote:
It doesn't care much what kind of memory it is, nor it's important
for internals how it's imported, it's user addresses -> pages for
user convenience sake. All the net_iov setup code is in
On 10/23/24 08:20, Christoph Hellwig wrote:
On Wed, Oct 16, 2024 at 11:52:39AM -0700, David Wei wrote:
From: Pavel Begunkov
Currently net_iov stores a pointer to struct dmabuf_genpool_chunk_owner,
which serves as a useful abstraction to share data and provide a
context. However, it's too devme
