From: Parav Pandit <parav@nvidia.com>
To: <netdev@vger.kernel.org>, <dsahern@kernel.org>,
<stephen@networkplumber.org>
Cc: <jiri@nvidia.com>, <shayd@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [PATCH 0/2] devlink: Support setting max_io_eqs
Date: Wed, 10 Apr 2024 10:39:01 +0300 [thread overview]
Message-ID: <20240410073903.7913-1-parav@nvidia.com> (raw)
Devices send event notifications for the IO queues,
such as tx and rx queues, through event queues.
Enable a privileged owner, such as a hypervisor PF, to set the number
of IO event queues for the VF and SF during the provisioning stage.
example:
Get maximum IO event queues of the VF device::
$ devlink port show pci/0000:06:00.0/2
pci/0000:06:00.0/2: type eth netdev enp6s0pf0vf1 flavour pcivf pfnum 0 vfnum 1
function:
hw_addr 00:00:00:00:00:00 ipsec_packet disabled max_io_eqs 10
Set maximum IO event queues of the VF device::
$ devlink port function set pci/0000:06:00.0/2 max_io_eqs 32
$ devlink port show pci/0000:06:00.0/2
pci/0000:06:00.0/2: type eth netdev enp6s0pf0vf1 flavour pcivf pfnum 0 vfnum 1
function:
hw_addr 00:00:00:00:00:00 ipsec_packet disabled max_io_eqs 32
patch summary:
patch-1 updates devlink uapi
patch-2 adds print, get and set routines for max_io_eqs field
Parav Pandit (2):
uapi: Update devlink kernel headers
devlink: Support setting max_io_eqs
devlink/devlink.c | 29 ++++++++++++++++++++++++++++-
include/uapi/linux/devlink.h | 1 +
2 files changed, 29 insertions(+), 1 deletion(-)
--
2.26.2
next reply other threads:[~2024-04-10 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 7:39 Parav Pandit [this message]
2024-04-10 7:39 ` [PATCH 1/2] uapi: Update devlink kernel headers Parav Pandit
2024-04-10 7:39 ` [PATCH 2/2] devlink: Support setting max_io_eqs Parav Pandit
2024-04-10 9:27 ` Jiri Pirko
2024-04-10 11:59 ` Parav Pandit
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=20240410073903.7913-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=dsahern@kernel.org \
--cc=jiri@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=shayd@nvidia.com \
--cc=stephen@networkplumber.org \
/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).