netdev - RE: [Intel-wired-lan] [PATCH iwl-next v10 09/10] idpf: avoid calling get_rx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <SJ1PR11MB62979BC8DF1A2B7F11E9781F9BA0A@SJ1PR11MB6297.namprd11.prod.outlook.com>
Date: Wed, 10 Dec 2025 23:21:57 +0000
From: "Salin, Samuel" <samuel.salin@...el.com>
To: "Loktionov, Aleksandr" <aleksandr.loktionov@...el.com>, "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 v10 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
> Loktionov, Aleksandr
> Sent: Wednesday, November 12, 2025 11:06 PM
> To: Hay, Joshua A <joshua.a.hay@...el.com>; intel-wired-lan@...ts.osuosl.org
> Cc: netdev@...r.kernel.org
> 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 <intel-wired-lan-bounces@...osl.org> On Behalf
> > Of Joshua Hay
> > Sent: Thursday, November 13, 2025 1:42 AM
> > To: intel-wired-lan@...ts.osuosl.org
> > Cc: netdev@...r.kernel.org
> > Subject: [Intel-wired-lan] [PATCH iwl-next v10 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
> 
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@...el.com>

Tested-by: Samuel Salin <Samuel.salin@...el.com>