Re: [PATCH net-next v10 02/14] net: page_pool: create hooks for custom page providers

[Pavel Begunkov]

On 6/18/24 07:43, Christoph Hellwig wrote:
> On Mon, Jun 17, 2024 at 07:04:43PM +0100, Pavel Begunkov wrote:
> > > There should be no other memory source other than the page allocator
> > > and dmabuf.  If you need different life time control for your
> > > zero copy proposal don't mix that up with the contol of the memory
> > > source.
> >
> > No idea how I'm mixing it up when I was explaining exactly this
> > all along as well as that the callback (and presumably the call
> > site in general) you was so eager to nack is used exactly to
> > implement the life time control.
>
> And that's exactly my point.  You want to use one callback to mix
> allocation source and life time control.  

No, it only takes the role of life time control and doesn't
care about the source. The allocation source step with
corresponding initialisation happens separately and
priorly, at initialisation time.

> That's the perfect recipe
> to create an un-extensible un-composable mess
--
Pavel Begunkov