[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHS8izPRqiaCmjsLG_tZRo-7W3xJ0QQmSQTQbYK-nkxx=9jmxw@mail.gmail.com>
Date: Wed, 20 Aug 2025 16:22:25 -0700
From: Mina Almasry <almasrymina@...gle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
michael.chan@...adcom.com, tariqt@...dia.com, dtatulea@...dia.com,
hawk@...nel.org, ilias.apalodimas@...aro.org, alexanderduyck@...com,
sdf@...ichev.me
Subject: Re: [PATCH net-next 05/15] eth: fbnic: use netmem_ref where applicable
On Tue, Aug 19, 2025 at 7:57 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> Use netmem_ref instead of struct page pointer in prep for
> unreadable memory. fbnic has separate free buffer submission
> queues for headers and for data. Refactor the helper which
> returns page pointer for a submission buffer to take the
> high level queue container, create a separate handler
> for header and payload rings. This ties the "upcast" from
> netmem to system page to use of sub0 which we know has
> system pages.
>
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
Reviewed-by: Mina Almasry <almasrymina@...gle.com>
--
Thanks,
Mina
Powered by blists - more mailing lists