[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <IA3PR11MB89863A24935B6C2B6425ECFAE5EBA@IA3PR11MB8986.namprd11.prod.outlook.com>
Date: Tue, 14 Oct 2025 07:50:59 +0000
From: "Loktionov, Aleksandr" <aleksandr.loktionov@...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 v8 8/9] 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 14, 2025 1:14 AM
> To: intel-wired-lan@...ts.osuosl.org
> Cc: netdev@...r.kernel.org
> Subject: [Intel-wired-lan] [PATCH iwl-next v8 8/9] 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
Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@...el.com>
Powered by blists - more mailing lists