> -----Original Message-----
> From: Intel-wired-lan <[email protected]> On Behalf Of 
> Michal Swiatkowski
> Sent: 04 November 2024 17:44
> To: [email protected]
> Cc: [email protected]; Drewek, Wojciech <[email protected]>; 
> Szycik, Marcin <[email protected]>; [email protected]; Knitter, 
> Konrad <[email protected]>; Chmielewski, Pawel 
> <[email protected]>; [email protected]; [email protected]; NEX 
> SW NCIS NAT HPM DEV <[email protected]>; 
> [email protected]; Samudrala, Sridhar <[email protected]>; 
> Keller, Jacob E <[email protected]>; [email protected]; Kitszel, 
> Przemyslaw <[email protected]>
> 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 <[email protected]>
> Reviewed-by: Wojciech Drewek <[email protected]>
> Signed-off-by: Michal Swiatkowski <[email protected]>
> ---
>  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 <[email protected]> (A 
Contingent worker at Intel)

Reply via email to