From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
linux-pci@vger.kernel.org, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, Don Dutile <ddutile@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Alexander Duyck <alexander.duyck@gmail.com>
Subject: Re: [PATCH mlx5-next v2 0/5] Dynamically assign MSI-X vectors count
Date: Thu, 14 Jan 2021 09:51:28 -0800 [thread overview]
Message-ID: <20210114095128.0f388f08@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210114103140.866141-1-leon@kernel.org>
On Thu, 14 Jan 2021 12:31:35 +0200 Leon Romanovsky wrote:
> The number of MSI-X vectors is PCI property visible through lspci, that
> field is read-only and configured by the device.
>
> The static assignment of an amount of MSI-X vectors doesn't allow utilize
> the newly created VF because it is not known to the device the future load
> and configuration where that VF will be used.
>
> The VFs are created on the hypervisor and forwarded to the VMs that have
> different properties (for example number of CPUs).
>
> To overcome the inefficiency in the spread of such MSI-X vectors, we
> allow the kernel to instruct the device with the needed number of such
> vectors, before VF is initialized and bounded to the driver.
Hi Leon!
Looks like you got some missing kdoc here, check out the test in
patchwork so we don't need to worry about this later:
https://patchwork.kernel.org/project/netdevbpf/list/?series=414497
next prev parent reply other threads:[~2021-01-14 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 10:31 [PATCH mlx5-next v2 0/5] Dynamically assign MSI-X vectors count Leon Romanovsky
2021-01-14 10:31 ` [PATCH mlx5-next v2 1/5] PCI: Add sysfs callback to allow MSI-X table size change of SR-IOV VFs Leon Romanovsky
2021-01-15 0:05 ` Alex Williamson
2021-01-16 8:23 ` Leon Romanovsky
2021-01-17 7:03 ` Leon Romanovsky
2021-01-14 10:31 ` [PATCH mlx5-next v2 2/5] PCI: Add SR-IOV sysfs entry to read total number of dynamic MSI-X vectors Leon Romanovsky
2021-01-15 0:05 ` Alex Williamson
2021-01-16 8:36 ` Leon Romanovsky
2021-01-14 10:31 ` [PATCH mlx5-next v2 3/5] net/mlx5: Add dynamic MSI-X capabilities bits Leon Romanovsky
2021-01-14 10:31 ` [PATCH mlx5-next v2 4/5] net/mlx5: Dynamically assign MSI-X vectors count Leon Romanovsky
2021-01-14 10:31 ` [PATCH mlx5-next v2 5/5] net/mlx5: Allow to the users to configure number of MSI-X vectors Leon Romanovsky
2021-01-14 17:51 ` Jakub Kicinski [this message]
2021-01-17 5:44 ` [PATCH mlx5-next v2 0/5] Dynamically assign MSI-X vectors count Leon Romanovsky
2021-01-17 7:24 ` Leon Romanovsky
2021-01-18 18:07 ` Jakub Kicinski
2021-01-19 5:39 ` Leon Romanovsky
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=20210114095128.0f388f08@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.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;
as well as URLs for NNTP newsgroup(s).