From: Eli Cohen <elic@nvidia.com>
To: <stephen@networkplumber.org>, <netdev@vger.kernel.org>
Cc: <jasowang@redhat.com>, <si-wei.liu@oracle.com>,
Eli Cohen <elic@nvidia.com>
Subject: [PATCH 0/3] vdpa tool support for configuring max VQs
Date: Mon, 7 Feb 2022 14:55:34 +0200 [thread overview]
Message-ID: <20220207125537.174619-1-elic@nvidia.com> (raw)
The following three patch series contains:
1. Small fix to vdpa help message
2. Introduce missing definitions for virtio feature flags so they can be
used in the 3rd patch.
3. Add support for configuring max number of VQs for a vdpa device and
allow to get negotiated or max features for a vdpa device/mangement
device.
Eli Cohen (3):
vdpa: Remove unsupported command line option
virtio: Define bit numbers for device independent features
vdpa: Add support to configure max number of VQs
include/uapi/linux/virtio_config.h | 16 ++--
vdpa/include/uapi/linux/vdpa.h | 4 +
vdpa/vdpa.c | 115 ++++++++++++++++++++++++++++-
3 files changed, 123 insertions(+), 12 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-07 13:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 12:55 Eli Cohen [this message]
2022-02-07 12:55 ` [PATCH 1/3] vdpa: Remove unsupported command line option Eli Cohen
2022-02-10 7:50 ` Jason Wang
2022-02-07 12:55 ` [PATCH 2/3] virtio: Define bit numbers for device independent features Eli Cohen
2022-02-10 7:54 ` Jason Wang
2022-02-10 8:30 ` Eli Cohen
2022-02-10 8:35 ` Jason Wang
2022-02-10 9:27 ` Eli Cohen
2022-02-14 6:06 ` Jason Wang
2022-02-16 7:15 ` Eli Cohen
2022-02-17 6:06 ` Jason Wang
2022-02-17 8:26 ` Eli Cohen
2022-02-07 12:55 ` [PATCH 3/3] vdpa: Add support to configure max number of VQs Eli Cohen
2022-02-10 8:07 ` Jason Wang
2022-02-10 8:44 ` Eli Cohen
2022-02-10 8:51 ` Jason Wang
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=20220207125537.174619-1-elic@nvidia.com \
--to=elic@nvidia.com \
--cc=jasowang@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 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).