From: Eli Cohen <elic@nvidia.com>
To: <stephen@networkplumber.org>, <netdev@vger.kernel.org>
Cc: <jasowang@redhat.com>, <lulu@redhat.com>, <si-wei.liu@oracle.com>,
"Eli Cohen" <elic@nvidia.com>
Subject: [PATCH v1 0/4] vdpa tool enhancements
Date: Thu, 10 Feb 2022 15:31:11 +0200 [thread overview]
Message-ID: <20220210133115.115967-1-elic@nvidia.com> (raw)
The following four patch series enhances vdpa to show negotiated
features for a vdpa device, max features for a management device and
allows to configure max number of virtqueue pairs.
v0 -> v1:
1. Split patches to present added functionality in separate patches.
2. Remove patch 0002 and add required definitions from uapi linux
headers.
3. Print bit numbers for non net devices.
Eli Cohen (4):
vdpa: Remove unsupported command line option
vdpa: Allow for printing negotiated features of a device
vdpa: Support for configuring max VQ pairs for a device
vdpa: Support reading device features
vdpa/include/uapi/linux/vdpa.h | 4 +
vdpa/vdpa.c | 164 +++++++++++++++++++++++++++++++--
2 files changed, 162 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-10 13:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 13:31 Eli Cohen [this message]
2022-02-10 13:31 ` [PATCH v1 1/4] vdpa: Remove unsupported command line option Eli Cohen
2022-02-12 0:44 ` Si-Wei Liu
2022-02-15 14:49 ` Eli Cohen
2022-02-10 13:31 ` [PATCH v1 2/4] vdpa: Allow for printing negotiated features of a device Eli Cohen
2022-02-12 1:15 ` Si-Wei Liu
2022-02-15 15:16 ` Eli Cohen
2022-02-16 21:42 ` Si-Wei Liu
2022-02-10 13:31 ` [PATCH v1 3/4] vdpa: Support for configuring max VQ pairs for " Eli Cohen
2022-02-12 0:37 ` Si-Wei Liu
2022-02-15 14:45 ` Eli Cohen
2022-02-10 13:31 ` [PATCH v1 4/4] vdpa: Support reading device features Eli Cohen
2022-02-12 0:43 ` Si-Wei Liu
2022-02-15 14:46 ` Eli Cohen
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=20220210133115.115967-1-elic@nvidia.com \
--to=elic@nvidia.com \
--cc=jasowang@redhat.com \
--cc=lulu@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=si-wei.liu@oracle.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 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.