From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, przemyslaw.kitszel@intel.com
Subject: [Intel-wired-lan] [PATCH iwl-next v1 0/4] change MSI-X vectors per VF
Date: Thu, 15 Jun 2023 14:38:26 +0200 [thread overview]
Message-ID: <20230615123830.155927-1-michal.swiatkowski@linux.intel.com> (raw)
Hi,
This patchset is implementing sysfs API introduced here [1].
It will allow user to assign different amount of MSI-X vectors to VF.
For example when there are VMs with different number of virtual cores.
Example:
1. Turn off autoprobe
echo 0 > /sys/bus/pci/devices/0000\:18\:00.0/sriov_drivers_autoprobe
2. Create VFs
echo 4 > /sys/bus/pci/devices/0000\:18\:00.0/sriov_numvfs
3. Configure MSI-X
echo 20 > /sys/class/pci_bus/0000\:18/device/0000\:18\:01.0/sriov_vf_msix_count
[1] https://lore.kernel.org/netdev/20210314124256.70253-1-leon@kernel.org/
Michal Swiatkowski (4):
ice: implement num_msix field per VF
ice: add bitmap to track VF MSI-X usage
ice: set MSI-X vector count on VF
ice: manage VFs MSI-X using resource tracking
drivers/net/ethernet/intel/ice/ice.h | 2 +
drivers/net/ethernet/intel/ice/ice_lib.c | 2 +-
drivers/net/ethernet/intel/ice/ice_main.c | 2 +
drivers/net/ethernet/intel/ice/ice_sriov.c | 257 ++++++++++++++++--
drivers/net/ethernet/intel/ice/ice_sriov.h | 13 +
drivers/net/ethernet/intel/ice/ice_vf_lib.h | 4 +-
drivers/net/ethernet/intel/ice/ice_virtchnl.c | 2 +-
7 files changed, 258 insertions(+), 24 deletions(-)
--
2.40.1
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2023-06-15 12:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 12:38 Michal Swiatkowski [this message]
2023-06-15 12:38 ` [Intel-wired-lan] [PATCH iwl-next v1 1/4] ice: implement num_msix field per VF Michal Swiatkowski
2023-06-15 14:22 ` Maciej Fijalkowski
2023-06-15 14:43 ` Michal Swiatkowski
2023-06-15 12:38 ` [Intel-wired-lan] [PATCH iwl-next v1 2/4] ice: add bitmap to track VF MSI-X usage Michal Swiatkowski
2023-06-15 12:38 ` [Intel-wired-lan] [PATCH iwl-next v1 3/4] ice: set MSI-X vector count on VF Michal Swiatkowski
2023-06-15 12:38 ` [Intel-wired-lan] [PATCH iwl-next v1 4/4] ice: manage VFs MSI-X using resource tracking Michal Swiatkowski
2023-06-15 15:57 ` Keller, Jacob E
2023-06-16 8:37 ` Michal Swiatkowski
2023-06-20 5:37 ` Keller, Jacob E
2023-11-23 17:22 ` Romanowski, Rafal
2023-06-16 20:37 ` [Intel-wired-lan] [PATCH iwl-next v1 0/4] change MSI-X vectors per VF Tony Nguyen
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=20230615123830.155927-1-michal.swiatkowski@linux.intel.com \
--to=michal.swiatkowski@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@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