[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1352787.1746625783@warthog.procyon.org.uk>
Date: Wed, 07 May 2025 14:49:43 +0100
From: David Howells <dhowells@...hat.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: dhowells@...hat.com, Jakub Kicinski <kuba@...nel.org>,
Andrew Lunn <andrew@...n.ch>, Eric Dumazet <edumazet@...gle.com>,
"David S. Miller" <davem@...emloft.net>,
David Hildenbrand <david@...hat.com>,
John Hubbard <jhubbard@...dia.com>, willy@...radead.org,
netdev@...r.kernel.org, linux-mm@...ck.org,
Willem de Bruijn <willemb@...gle.com>
Subject: Re: Reorganising how the networking layer handles memory
Christoph Hellwig <hch@...radead.org> wrote:
> > Christoph Hellwig would like to make it such that the extractor gets
> > {phyaddr,len} rather than {page,off,len} - so all you, the network layer,
> > see is that you've got a span of memory to use as your buffer. How that
> > span of memory is managed is the responsibility of whoever called
> > sendmsg() - and they need a callback to be able to handle that.
>
> Not sure what the extractor is
Just a function that tries to get information out of the iov_iter. In the
case of the networking layer, something like zerocopy_fill_skb_from_iter()
that calls iov_iter_get_pages2() currently.
David
Powered by blists - more mailing lists