> -----Original Message-----
> From: Intel-wired-lan <[email protected]> On Behalf Of
> Loktionov, Aleksandr
> Sent: Wednesday, November 12, 2025 11:06 PM
> To: Hay, Joshua A <[email protected]>; [email protected]
> Cc: [email protected]
> Subject: Re: [Intel-wired-lan] [PATCH iwl-next v10 09/10] idpf: avoid calling
> get_rx_ptypes for each vport
>
>
>
> > -----Original Message-----
> > From: Intel-wired-lan <[email protected]> On Behalf
> > Of Joshua Hay
> > Sent: Thursday, November 13, 2025 1:42 AM
> > To: [email protected]
> > Cc: [email protected]
> > Subject: [Intel-wired-lan] [PATCH iwl-next v10 09/10] idpf: avoid
> > calling get_rx_ptypes for each vport
> >
> > From: Pavan Kumar Linga <[email protected]>
> >
> > 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 <[email protected]>
> > Signed-off-by: Pavan Kumar Linga <[email protected]>
> > Signed-off-by: Joshua Hay <[email protected]>
> > ---
> > v8: rebase on AF_XDP series
> > ---
>
> ...
>
> > --
> > 2.39.2
>
> Reviewed-by: Aleksandr Loktionov <[email protected]>
Tested-by: Samuel Salin <[email protected]>
