> -----Original Message----- > From: Intel-wired-lan <intel-wired-lan-boun...@osuosl.org> On Behalf Of > Michal Swiatkowski > Sent: 04 November 2024 17:44 > To: intel-wired-...@lists.osuosl.org > Cc: pmen...@molgen.mpg.de; Drewek, Wojciech <wojciech.dre...@intel.com>; > Szycik, Marcin <marcin.szy...@intel.com>; net...@vger.kernel.org; Knitter, > Konrad <konrad.knit...@intel.com>; Chmielewski, Pawel > <pawel.chmielew...@intel.com>; ho...@kernel.org; david.lai...@aculab.com; NEX > SW NCIS NAT HPM DEV <nex.sw.ncis.nat.hpm....@intel.com>; > pio.raczyn...@gmail.com; Samudrala, Sridhar <sridhar.samudr...@intel.com>; > Keller, Jacob E <jacob.e.kel...@intel.com>; j...@resnulli.us; Kitszel, > Przemyslaw <przemyslaw.kits...@intel.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.kel...@intel.com> > Reviewed-by: Wojciech Drewek <wojciech.dre...@intel.com> > Signed-off-by: Michal Swiatkowski <michal.swiatkow...@linux.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.pu...@intel.com> (A Contingent worker at Intel)
