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: <SJ1PR11MB6297ECF44A1B0738F39C26BA9B9EA@SJ1PR11MB6297.namprd11.prod.outlook.com>
Date: Wed, 21 May 2025 23:08:05 +0000
From: "Salin, Samuel" <samuel.salin@...el.com>
To: "Linga, Pavan Kumar" <pavan.kumar.linga@...el.com>,
	"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "Olech, Milena"
	<milena.olech@...el.com>, "Nadezhdin, Anton" <anton.nadezhdin@...el.com>,
	"Linga, Pavan Kumar" <pavan.kumar.linga@...el.com>, "Chittim, Madhu"
	<madhu.chittim@...el.com>
Subject: RE: [Intel-wired-lan] [PATCH iwl-next v4 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
> Pavan Kumar Linga
> Sent: Thursday, May 8, 2025 2:50 PM
> To: intel-wired-lan@...ts.osuosl.org
> Cc: netdev@...r.kernel.org; Olech, Milena <milena.olech@...el.com>;
> Nadezhdin, Anton <anton.nadezhdin@...el.com>; Linga, Pavan Kumar
> <pavan.kumar.linga@...el.com>; Chittim, Madhu
> <madhu.chittim@...el.com>
> Subject: [Intel-wired-lan] [PATCH iwl-next v4 8/9] idpf: avoid calling
> get_rx_ptypes for each vport
> 
> 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>
> ---
> 2.43.0

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ