[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221114210856.0d76bb2c@kernel.org>
Date: Mon, 14 Nov 2022 21:08:56 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, pabeni@...hat.com,
edumazet@...gle.com, intel-wired-lan@...ts.osuosl.org,
jiri@...dia.com, anthony.l.nguyen@...el.com,
alexandr.lobakin@...el.com, sridhar.samudrala@...el.com,
wojciech.drewek@...el.com, lukasz.czapnik@...el.com,
shiraz.saleem@...el.com, jesse.brandeburg@...el.com,
mustafa.ismail@...el.com, przemyslaw.kitszel@...el.com,
piotr.raczynski@...el.com, jacob.e.keller@...el.com,
david.m.ertman@...el.com, leszek.kaliszczuk@...el.com
Subject: Re: [PATCH net-next 12/13] ice, irdma: prepare reservation of MSI-X
to reload
On Mon, 14 Nov 2022 13:57:54 +0100 Michal Swiatkowski wrote:
> Move MSI-X number for LAN and RDMA to structure to have it in one
> place. Use req_msix to store how many MSI-X for each feature user
> requested. Structure msix is used to store the current number of MSI-X.
>
> The MSI-X number needs to be adjust if kernel doesn't support that many
> MSI-X or if hardware doesn't support it. Rewrite MSI-X adjustment
> function to use it in both cases.
>
> Use the same algorithm like previously. First allocate minimum MSI-X for
> each feature than if there is enough MSI-X distribute it equally between
> each one.
drivers/net/ethernet/intel/ice/ice_lib.c:455: warning: Function parameter or member 'vsi' not described in 'ice_vsi_alloc_def'
drivers/net/ethernet/intel/ice/ice_lib.c:455: warning: Excess function parameter 'vsi_type' description in 'ice_vsi_alloc_def'
drivers/net/ethernet/intel/ice/ice_main.c:4026:9: warning: variable 'err' is uninitialized when used here [-Wuninitialized]
return err;
^~~
drivers/net/ethernet/intel/ice/ice_main.c:4001:29: note: initialize the variable 'err' to silence this warning
int v_wanted, v_actual, err, i;
^
= 0
Powered by blists - more mailing lists