netdev - RE: [Intel-wired-lan] [iwl-next v7 6/9] ice: treat dyn

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] [day] [month] [year] [list]

Message-ID: <CYYPR11MB842967FDC9362FF15886916DBD5B2@CYYPR11MB8429.namprd11.prod.outlook.com>
Date: Thu, 14 Nov 2024 14:09:54 +0000
From: "Pucha, HimasekharX Reddy" <himasekharx.reddy.pucha@...el.com>
To: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>,
	"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
CC: "pmenzel@...gen.mpg.de" <pmenzel@...gen.mpg.de>, "Drewek, Wojciech"
	<wojciech.drewek@...el.com>, "Szycik, Marcin" <marcin.szycik@...el.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>, "Knitter, Konrad"
	<konrad.knitter@...el.com>, "Chmielewski, Pawel"
	<pawel.chmielewski@...el.com>, "horms@...nel.org" <horms@...nel.org>,
	"David.Laight@...LAB.COM" <David.Laight@...LAB.COM>, NEX SW NCIS NAT HPM DEV
	<nex.sw.ncis.nat.hpm.dev@...el.com>, "pio.raczynski@...il.com"
	<pio.raczynski@...il.com>, "Samudrala, Sridhar"
	<sridhar.samudrala@...el.com>, "Keller, Jacob E" <jacob.e.keller@...el.com>,
	"jiri@...nulli.us" <jiri@...nulli.us>, "Kitszel, Przemyslaw"
	<przemyslaw.kitszel@...el.com>
Subject: RE: [Intel-wired-lan] [iwl-next v7 6/9] ice: treat dyn_allowed only
 as suggestion

> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of Michal Swiatkowski
> Sent: 04 November 2024 17:44
> To: intel-wired-lan@...ts.osuosl.org
> Cc: pmenzel@...gen.mpg.de; Drewek, Wojciech <wojciech.drewek@...el.com>; Szycik, Marcin <marcin.szycik@...el.com>; netdev@...r.kernel.org; Knitter, Konrad <konrad.knitter@...el.com>; Chmielewski, Pawel <pawel.chmielewski@...el.com>; horms@...nel.org; David.Laight@...LAB.COM; NEX SW NCIS NAT HPM DEV <nex.sw.ncis.nat.hpm.dev@...el.com>; pio.raczynski@...il.com; Samudrala, Sridhar <sridhar.samudrala@...el.com>; Keller, Jacob E <jacob.e.keller@...el.com>; jiri@...nulli.us; Kitszel, Przemyslaw <przemyslaw.kitszel@...el.com>
> Subject: [Intel-wired-lan] [iwl-next v7 6/9] ice: treat dyn_allowed only as suggestion
>
> It can be needed to have some MSI-X allocated as static and rest as dynamic. For example on PF VSI. We want to always have minimum one MSI-X on it, because of that it is allocated as a static one, rest can be dynamic if it is supported.
>
> Change the ice_get_irq_res() to allow using static entries if they are free even if caller wants dynamic one.
>
> Adjust limit values to the new approach. Min and max in limit means the values that are valid, so decrease max and num_static by one.
>
> Set vsi::irq_dyn_alloc if dynamic allocation is supported.
>
> Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
> Reviewed-by: Wojciech Drewek <wojciech.drewek@...el.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>
> ---
>  drivers/net/ethernet/intel/ice/ice_irq.c | 25 ++++++++++++------------  drivers/net/ethernet/intel/ice/ice_lib.c |  2 ++
>  2 files changed, 15 insertions(+), 12 deletions(-)
>

Tested-by: Pucha Himasekhar Reddy <himasekharx.reddy.pucha@...el.com> (A Contingent worker at Intel)