[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ad5eaaa5-0ee8-036b-d830-18c10039c41f@intel.com>
Date: Fri, 16 Jun 2023 13:37:35 -0700
From: Tony Nguyen <anthony.l.nguyen@...el.com>
To: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>,
<intel-wired-lan@...ts.osuosl.org>
CC: <netdev@...r.kernel.org>, <przemyslaw.kitszel@...el.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 0/4] change MSI-X vectors
per VF
On 6/15/2023 5:38 AM, Michal Swiatkowski wrote:
> 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(-)
This doesn't apply to net-queue, however, it seems as though it applies
to net-next. Please use the tree that you are targeting to base your
patches on. While most the time it may not matter, in some cases, like
this, it does.
Thanks,
Tony
Powered by blists - more mailing lists