[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240612141105.16880cde@kernel.org>
Date: Wed, 12 Jun 2024 14:11:05 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: David Wei <dw@...idwei.uk>
Cc: David Ahern <dsahern@...nel.org>, Michael Chan
<michael.chan@...adcom.com>, Andy Gospodarek
<andrew.gospodarek@...adcom.com>, Adrian Alvarado
<adrian.alvarado@...adcom.com>, Somnath Kotur <somnath.kotur@...adcom.com>,
netdev@...r.kernel.org, Pavel Begunkov <asml.silence@...il.com>, "David S.
Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next v1 0/3] bnxt_en: implement
netdev_queue_mgmt_ops
On Wed, 12 Jun 2024 11:19:47 -0700 David Wei wrote:
> Any validation would be done outside of this patchset, which only
> focuses on resetting an Rx queue. Reconfiguring page pools and HDS is
> orthogonal and unrelated to this patchset.
>
> The netdev core API consuming netdev_queue_mgmt_ops would be
> netdev_rx_queue_restart() added in [1].
>
> [1]: https://lore.kernel.org/lkml/20240607005127.3078656-2-almasrymina@google.com/
>
> Validation would be done at a layer above, i.e. whatever that calls
> netdev_rx_queue_restart(), as opposed to netdev_rx_queue_restart() or
> netdev_queue_mgmt_ops itself.
One could be tempted to pass a "configuration" object to tell the
driver that this queue will be required to run with HDS enabled.
I wonder where I've seen such a thing...
Powered by blists - more mailing lists