[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6297C190A139FF26260522519BC7A@SJ1PR11MB6297.namprd11.prod.outlook.com>
Date: Mon, 3 Nov 2025 15:28:46 +0000
From: "Salin, Samuel" <samuel.salin@...el.com>
To: "Hay, Joshua A" <joshua.a.hay@...el.com>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [Intel-wired-lan] [PATCH iwl-next v9 09/10] idpf: avoid calling
get_rx_ptypes for each vport
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of
> Joshua Hay
> Sent: Tuesday, October 21, 2025 4:31 PM
> To: intel-wired-lan@...ts.osuosl.org
> Cc: netdev@...r.kernel.org
> Subject: [Intel-wired-lan] [PATCH iwl-next v9 09/10] idpf: avoid calling
> get_rx_ptypes for each vport
>
> From: Pavan Kumar Linga <pavan.kumar.linga@...el.com>
>
> RX ptypes received from device control plane doesn't depend on vport info,
> but might vary based on the queue model. When the driver requests for
> ptypes, control plane fills both ptype_id_10 (used for splitq) and
> ptype_id_8 (used for singleq) fields of the virtchnl2_ptype response structure.
> This allows to call get_rx_ptypes once at the adapter level instead of each
> vport.
>
> Parse and store the received ptypes of both splitq and singleq in a separate
> lookup table. Respective lookup table is used based on the queue model info.
> As part of the changes, pull the ptype protocol parsing code into a separate
> function.
>
> Reviewed-by: Madhu Chittim <madhu.chittim@...el.com>
> Signed-off-by: Pavan Kumar Linga <pavan.kumar.linga@...el.com>
> Signed-off-by: Joshua Hay <joshua.a.hay@...el.com>
> ---
> v8: rebase on AF_XDP series
> ---
> 2.39.2
Tested-by: Samuel Salin <Samuel.salin@...el.com>
Powered by blists - more mailing lists