[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d3029215-1ab9-4503-bddd-6dfce10e8e5d@nvidia.com>
Date: Tue, 8 Jul 2025 19:03:25 +0300
From: Gal Pressman <gal@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>, davem@...emloft.net
Cc: netdev@...r.kernel.org, edumazet@...gle.com, pabeni@...hat.com,
andrew+netdev@...n.ch, horms@...nel.org, andrew@...n.ch,
przemyslaw.kitszel@...el.com, anthony.l.nguyen@...el.com,
sgoutham@...vell.com, gakula@...vell.com, sbhatta@...vell.com,
bbhushan2@...vell.com, tariqt@...dia.com, mbloch@...dia.com,
leon@...nel.org, ecree.xilinx@...il.com
Subject: Re: [PATCH net-next v3 3/5] eth: mlx5: migrate to the *_rxfh_context
ops
On 07/07/2025 21:41, Jakub Kicinski wrote:
> Convert mlx5 to dedicated RXFH ops. This is a fairly shallow
> conversion, TBH, most of the driver code stays as is, but we
> let the core allocate the context ID for the driver.
>
> mlx5e_rx_res_rss_get_rxfh() and friends are made void, since
> core only calls the driver for context 0. The second call
> is right after context creation so it must exist (tm).
>
> Tested with drivers/net/hw/rss_ctx.py on MCX6.
>
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
Thanks!
Reviewed-by: Gal Pressman <gal@...dia.com>
Powered by blists - more mailing lists