From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, pawel.chmielewski@intel.com,
sridhar.samudrala@intel.com, jacob.e.keller@intel.com,
pio.raczynski@gmail.com, konrad.knitter@intel.com,
marcin.szycik@intel.com, wojciech.drewek@intel.com,
nex.sw.ncis.nat.hpm.dev@intel.com, przemyslaw.kitszel@intel.com,
jiri@resnulli.us, horms@kernel.org, David.Laight@aculab.com
Subject: Re: [Intel-wired-lan] [iwl-next v5 2/9] ice: devlink PF MSI-X max and min parameter
Date: Mon, 28 Oct 2024 07:10:12 +0100 [thread overview]
Message-ID: <Zx8qxF+4EPQZnO0k@mev-dev.igk.intel.com> (raw)
In-Reply-To: <20241024121230.5861-3-michal.swiatkowski@linux.intel.com>
On Thu, Oct 24, 2024 at 02:12:23PM +0200, Michal Swiatkowski wrote:
> Use generic devlink PF MSI-X parameter to allow user to change MSI-X
> range.
>
> Add notes about this parameters into ice devlink documentation.
>
> Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> ---
> Documentation/networking/devlink/ice.rst | 11 +++
> .../net/ethernet/intel/ice/devlink/devlink.c | 83 ++++++++++++++++++-
> drivers/net/ethernet/intel/ice/ice.h | 7 ++
> drivers/net/ethernet/intel/ice/ice_irq.c | 7 ++
> 4 files changed, 107 insertions(+), 1 deletion(-)
>
[...]
> diff --git a/drivers/net/ethernet/intel/ice/ice_irq.c b/drivers/net/ethernet/intel/ice/ice_irq.c
> index ad82ff7d1995..0659b96b9b8c 100644
> --- a/drivers/net/ethernet/intel/ice/ice_irq.c
> +++ b/drivers/net/ethernet/intel/ice/ice_irq.c
> @@ -254,6 +254,13 @@ int ice_init_interrupt_scheme(struct ice_pf *pf)
> int total_vectors = pf->hw.func_caps.common_cap.num_msix_vectors;
> int vectors, max_vectors;
>
> + /* load default PF MSI-X range */
> + if (!pf->msix.min)
> + pf->msix.min = ICE_MIN_MSIX;
> +
> + if (!pf->msix.max)
> + pf->msix.max = total_vectors / 2;
Probably it will be better to set max to the value that PF needs after
calling ice_ena_msix_range(). I will send next version with that change,
please not pull.
Thanks,
Michal
> +
> vectors = ice_ena_msix_range(pf);
>
> if (vectors < 0)
> --
> 2.42.0
>
next prev parent reply other threads:[~2024-10-28 6:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 12:12 [Intel-wired-lan] [iwl-next v5 0/9] ice: managing MSI-X in driver Michal Swiatkowski
2024-10-24 12:12 ` [Intel-wired-lan] [iwl-next v5 1/9] ice: count combined queues using Rx/Tx count Michal Swiatkowski
2024-10-24 12:12 ` [Intel-wired-lan] [iwl-next v5 2/9] ice: devlink PF MSI-X max and min parameter Michal Swiatkowski
2024-10-28 6:10 ` Michal Swiatkowski [this message]
2024-10-24 12:12 ` [Intel-wired-lan] [iwl-next v5 3/9] ice: remove splitting MSI-X between features Michal Swiatkowski
2024-10-24 12:12 ` [Intel-wired-lan] [iwl-next v5 4/9] ice: get rid of num_lan_msix field Michal Swiatkowski
2024-10-24 12:12 ` [Intel-wired-lan] [iwl-next v5 5/9] ice, irdma: move interrupts code to irdma Michal Swiatkowski
2024-10-24 12:12 ` [Intel-wired-lan] [iwl-next v5 6/9] ice: treat dyn_allowed only as suggestion Michal Swiatkowski
2024-10-24 12:12 ` [Intel-wired-lan] [iwl-next v5 7/9] ice: enable_rdma devlink param Michal Swiatkowski
2024-10-24 12:12 ` [Intel-wired-lan] [iwl-next v5 8/9] ice: simplify VF MSI-X managing Michal Swiatkowski
2024-10-24 12:12 ` [Intel-wired-lan] [iwl-next v5 9/9] ice: init flow director before RDMA Michal Swiatkowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zx8qxF+4EPQZnO0k@mev-dev.igk.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=David.Laight@aculab.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=konrad.knitter@intel.com \
--cc=marcin.szycik@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nex.sw.ncis.nat.hpm.dev@intel.com \
--cc=pawel.chmielewski@intel.com \
--cc=pio.raczynski@gmail.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=wojciech.drewek@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox