[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240110173523.012175fd@kernel.org>
Date: Wed, 10 Jan 2024 17:35:23 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Shakeel Butt <shakeelb@...gle.com>
Cc: Mina Almasry <almasrymina@...gle.com>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, kvm@...r.kernel.org,
virtualization@...ts.linux.dev, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Stefan
Hajnoczi <stefanha@...hat.com>, Stefano Garzarella <sgarzare@...hat.com>,
David Howells <dhowells@...hat.com>, Jason Gunthorpe <jgg@...dia.com>,
Christian König <christian.koenig@....com>, Yunsheng Lin
<linyunsheng@...wei.com>, Willem de Bruijn
<willemdebruijn.kernel@...il.com>
Subject: Re: [PATCH net-next v3 2/3] net: introduce abstraction for network
memory
On Wed, 10 Jan 2024 09:50:08 -0800 Shakeel Butt wrote:
> On Thu, Jan 4, 2024 at 1:44 PM Jakub Kicinski <kuba@...nel.org> wrote:
> > You seem to be trying hard to make struct netmem a thing.
> > Perhaps you have a reason I'm not getting?
>
> Mina already went with your suggestion and that is fine. To me, struct
> netmem is more aesthetically aligned with the existing struct
> encoded_page approach, but I don't have a strong opinion one way or
> the other. However it seems like you have a stronger preference for
> __bitwise approach. Is there a technical reason or just aesthetic?
Yes, right above the text you quoted:
The __bitwise annotation will make catching people trying
to cast to struct page * trivial.
https://lore.kernel.org/all/20240104134424.399fee0a@kernel.org/
Powered by blists - more mailing lists