All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@nvidia.com>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: mustafa.ismail@intel.com, netdev@vger.kernel.org,
	leszek.kaliszczuk@intel.com, przemyslaw.kitszel@intel.com,
	edumazet@google.com, Michal Kubiak <michal.kubiak@intel.com>,
	intel-wired-lan@lists.osuosl.org, kuba@kernel.org,
	pabeni@redhat.com, shiraz.saleem@intel.com, davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next 13/13] devlink, ice: add MSIX vectors as devlink resource
Date: Mon, 14 Nov 2022 16:28:38 +0100	[thread overview]
Message-ID: <Y3Jepn7bxkCFP+cg@nanopsycho> (raw)
In-Reply-To: <20221114125755.13659-14-michal.swiatkowski@linux.intel.com>

Mon, Nov 14, 2022 at 01:57:55PM CET, michal.swiatkowski@linux.intel.com wrote:
>From: Michal Kubiak <michal.kubiak@intel.com>
>
>Implement devlink resource to control how many MSI-X vectors are
>used for eth, VF and RDMA. Show misc MSI-X as read only.
>
>This is first approach to control the mix of resources managed
>by ice driver. This commit registers number of available MSI-X
>as devlink resource and also add specific resources for eth, vf and RDMA.
>
>Also, make those resources generic.
>
>$ devlink resource show pci/0000:31:00.0
>  name msix size 1024 occ 172 unit entry dpipe_tables none


So, 1024 is the total vector count available in your hw?


>    resources:
>      name msix_misc size 4 unit entry dpipe_tables none

What's misc? Why you don't show occupancy for it? Yet, it seems to be
accounted in the total (172)

Also, drop the "msix_" prefix from all, you already have parent called
"msix".


>      name msix_eth size 92 occ 92 unit entry size_min 1 size_max

Why "size_min is not 0 here?


>	128 size_gran 1 dpipe_tables none
>      name msix_vf size 128 occ 0 unit entry size_min 0 size_max
>	1020 size_gran 1 dpipe_tables none
>      name msix_rdma size 76 occ 76 unit entry size_min 0 size_max

Okay, this means that for eth and rdma, the vectors are fully used, no
VF is instanciated?



>	132 size_gran 1 dpipe_tables none
>
>example commands:
>$ devlink resource set pci/0000:31:00.0 path msix/msix_eth size 16
>$ devlink resource set pci/0000:31:00.0 path msix/msix_vf size 512
>$ devlink dev reload pci/0000:31:00.0
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: Jiri Pirko <jiri@nvidia.com>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com,
	intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
	alexandr.lobakin@intel.com, sridhar.samudrala@intel.com,
	wojciech.drewek@intel.com, lukasz.czapnik@intel.com,
	shiraz.saleem@intel.com, jesse.brandeburg@intel.com,
	mustafa.ismail@intel.com, przemyslaw.kitszel@intel.com,
	piotr.raczynski@intel.com, jacob.e.keller@intel.com,
	david.m.ertman@intel.com, leszek.kaliszczuk@intel.com,
	Michal Kubiak <michal.kubiak@intel.com>
Subject: Re: [PATCH net-next 13/13] devlink, ice: add MSIX vectors as devlink resource
Date: Mon, 14 Nov 2022 16:28:38 +0100	[thread overview]
Message-ID: <Y3Jepn7bxkCFP+cg@nanopsycho> (raw)
In-Reply-To: <20221114125755.13659-14-michal.swiatkowski@linux.intel.com>

Mon, Nov 14, 2022 at 01:57:55PM CET, michal.swiatkowski@linux.intel.com wrote:
>From: Michal Kubiak <michal.kubiak@intel.com>
>
>Implement devlink resource to control how many MSI-X vectors are
>used for eth, VF and RDMA. Show misc MSI-X as read only.
>
>This is first approach to control the mix of resources managed
>by ice driver. This commit registers number of available MSI-X
>as devlink resource and also add specific resources for eth, vf and RDMA.
>
>Also, make those resources generic.
>
>$ devlink resource show pci/0000:31:00.0
>  name msix size 1024 occ 172 unit entry dpipe_tables none


So, 1024 is the total vector count available in your hw?


>    resources:
>      name msix_misc size 4 unit entry dpipe_tables none

What's misc? Why you don't show occupancy for it? Yet, it seems to be
accounted in the total (172)

Also, drop the "msix_" prefix from all, you already have parent called
"msix".


>      name msix_eth size 92 occ 92 unit entry size_min 1 size_max

Why "size_min is not 0 here?


>	128 size_gran 1 dpipe_tables none
>      name msix_vf size 128 occ 0 unit entry size_min 0 size_max
>	1020 size_gran 1 dpipe_tables none
>      name msix_rdma size 76 occ 76 unit entry size_min 0 size_max

Okay, this means that for eth and rdma, the vectors are fully used, no
VF is instanciated?



>	132 size_gran 1 dpipe_tables none
>
>example commands:
>$ devlink resource set pci/0000:31:00.0 path msix/msix_eth size 16
>$ devlink resource set pci/0000:31:00.0 path msix/msix_vf size 512
>$ devlink dev reload pci/0000:31:00.0

  reply	other threads:[~2022-11-14 16:09 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 12:57 [Intel-wired-lan] [PATCH net-next 00/13] resource management using devlink reload Michal Swiatkowski
2022-11-14 12:57 ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 01/13] ice: move RDMA init to ice_idc.c Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 02/13] ice: alloc id for RDMA using xa_array Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 03/13] ice: cleanup in VSI config/deconfig code Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 04/13] ice: split ice_vsi_setup into smaller functions Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-15  5:08   ` [Intel-wired-lan] " Jakub Kicinski
2022-11-15  5:08     ` Jakub Kicinski
2022-11-15  6:49     ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-15  6:49       ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 05/13] ice: stop hard coding the ICE_VSI_CTRL location Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 06/13] ice: split probe into smaller functions Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 07/13] ice: sync netdev filters after clearing VSI Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 08/13] ice: move VSI delete outside deconfig Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 09/13] ice: update VSI instead of init in some case Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 10/13] ice: implement devlink reinit action Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 11/13] ice: introduce eswitch capable flag Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 12/13] ice, irdma: prepare reservation of MSI-X to reload Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-15  5:08   ` [Intel-wired-lan] " Jakub Kicinski
2022-11-15  5:08     ` Jakub Kicinski
2022-11-15  6:49     ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-15  6:49       ` Michal Swiatkowski
2022-11-14 12:57 ` [Intel-wired-lan] [PATCH net-next 13/13] devlink, ice: add MSIX vectors as devlink resource Michal Swiatkowski
2022-11-14 12:57   ` Michal Swiatkowski
2022-11-14 15:28   ` Jiri Pirko [this message]
2022-11-14 15:28     ` Jiri Pirko
2022-11-14 16:03     ` [Intel-wired-lan] " Piotr Raczynski
2022-11-14 16:03       ` Piotr Raczynski
2022-11-15  6:56       ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-15  6:56         ` Michal Swiatkowski
2022-11-15 12:08       ` [Intel-wired-lan] " Jiri Pirko
2022-11-15 12:08         ` Jiri Pirko
2022-11-14 13:23 ` [Intel-wired-lan] [PATCH net-next 00/13] resource management using devlink reload Leon Romanovsky
2022-11-14 13:23   ` Leon Romanovsky
2022-11-14 15:31   ` [Intel-wired-lan] " Samudrala, Sridhar
2022-11-14 15:31     ` Samudrala, Sridhar
2022-11-14 16:58     ` [Intel-wired-lan] " Keller, Jacob E
2022-11-14 16:58       ` Keller, Jacob E
2022-11-14 17:09       ` [Intel-wired-lan] " Leon Romanovsky
2022-11-14 17:09         ` Leon Romanovsky
2022-11-15  7:00         ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-15  7:00           ` Michal Swiatkowski
2022-11-14 17:07     ` [Intel-wired-lan] " Leon Romanovsky
2022-11-14 17:07       ` Leon Romanovsky
2022-11-15  7:12       ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-15  7:12         ` Michal Swiatkowski
2022-11-15  8:11         ` [Intel-wired-lan] " Leon Romanovsky
2022-11-15  8:11           ` Leon Romanovsky
2022-11-15  9:04           ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-15  9:04             ` Michal Swiatkowski
2022-11-15  9:32             ` [Intel-wired-lan] " Leon Romanovsky
2022-11-15  9:32               ` Leon Romanovsky
2022-11-15 10:16               ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-15 10:16                 ` Michal Swiatkowski
2022-11-15 12:12                 ` [Intel-wired-lan] " Leon Romanovsky
2022-11-15 12:12                   ` Leon Romanovsky
2022-11-15 14:02                   ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-15 14:02                     ` Michal Swiatkowski
2022-11-15 17:57                     ` [Intel-wired-lan] " Leon Romanovsky
2022-11-15 17:57                       ` Leon Romanovsky
2022-11-16  1:59                       ` [Intel-wired-lan] " Samudrala, Sridhar
2022-11-16  1:59                         ` Samudrala, Sridhar
2022-11-16  6:04                         ` [Intel-wired-lan] " Leon Romanovsky
2022-11-16  6:04                           ` Leon Romanovsky
2022-11-16 12:04                           ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-16 12:04                             ` Michal Swiatkowski
2022-11-16 17:59                             ` [Intel-wired-lan] " Leon Romanovsky
2022-11-16 17:59                               ` Leon Romanovsky
2022-11-17 11:10                               ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-17 11:10                                 ` Michal Swiatkowski
2022-11-17 11:45                                 ` [Intel-wired-lan] " Leon Romanovsky
2022-11-17 11:45                                   ` Leon Romanovsky
2022-11-17 13:39                                   ` [Intel-wired-lan] " Michal Swiatkowski
2022-11-17 13:39                                     ` Michal Swiatkowski
2022-11-17 17:38                                     ` [Intel-wired-lan] " Leon Romanovsky
2022-11-17 17:38                                       ` Leon Romanovsky
2022-11-18  3:36                                       ` [Intel-wired-lan] " Jakub Kicinski
2022-11-18  3:36                                         ` Jakub Kicinski
2022-11-18  6:20                                         ` [Intel-wired-lan] " Leon Romanovsky
2022-11-18  6:20                                           ` Leon Romanovsky
2022-11-18 14:23                                           ` [Intel-wired-lan] " Saleem, Shiraz
2022-11-18 14:23                                             ` Saleem, Shiraz
2022-11-18 17:31                                             ` [Intel-wired-lan] " Leon Romanovsky
2022-11-18 17:31                                               ` Leon Romanovsky
2022-11-20 22:24                                               ` [Intel-wired-lan] " Samudrala, Sridhar
2022-11-20 22:24                                                 ` Samudrala, Sridhar

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=Y3Jepn7bxkCFP+cg@nanopsycho \
    --to=jiri@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=leszek.kaliszczuk@intel.com \
    --cc=michal.kubiak@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=mustafa.ismail@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=shiraz.saleem@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.