From: Eli Cohen <elic@nvidia.com>
To: <mst@redhat.com>, <jasowang@redhat.com>
Cc: <virtualization@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <si-wei.liu@oracle.com>,
Eli Cohen <elic@nvidia.com>
Subject: [PATCH v4 0/3] Show statistics for a vdpa device
Date: Sun, 8 May 2022 19:33:14 +0300 [thread overview]
Message-ID: <20220508163317.204673-1-elic@nvidia.com> (raw)
The following three patch series adds support to read vendor statistics
for a vdpa device.
The first patch is just a cleanup fix.
The second patch lays the ground to allow an upstream driver to provide
statistics in the form of an attribute name/attribute value pairs.
The third patch implements this for mlx5_vdpa which gives received
descriptors and completed descriptors information for all the
virtqueues.
Jason, I removed your ack from the mlx5 patch since I modified it a bit.
I am sending the userspace patch I was using following this series.
Eli Cohen (3):
vdpa: Fix error logic in vdpa_nl_cmd_dev_get_doit
vdpa: Add support for querying vendor statistics
vdpa/mlx5: Add support for reading descriptor statistics
v3 -> v4:
Add a small cleanup fix patch
Only return statistics if feature negotiation is complete.
drivers/vdpa/mlx5/core/mlx5_vdpa.h | 2 +
drivers/vdpa/mlx5/net/mlx5_vnet.c | 171 +++++++++++++++++++++++++++++
drivers/vdpa/vdpa.c | 143 +++++++++++++++++++++++-
include/linux/mlx5/mlx5_ifc.h | 1 +
include/linux/mlx5/mlx5_ifc_vdpa.h | 39 +++++++
include/linux/vdpa.h | 5 +
include/uapi/linux/vdpa.h | 6 +
7 files changed, 363 insertions(+), 4 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-08 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 16:33 Eli Cohen [this message]
2022-05-08 16:33 ` [PATCH v4 1/3] vdpa: Fix error logic in vdpa_nl_cmd_dev_get_doit Eli Cohen
2022-05-10 2:40 ` Jason Wang
2022-05-08 16:33 ` [PATCH v4 2/3] vdpa: Add support for querying vendor statistics Eli Cohen
2022-05-08 16:33 ` [PATCH v4 3/3] vdpa/mlx5: Add support for reading descriptor statistics Eli Cohen
2022-05-10 3:01 ` Jason Wang
2022-05-10 6:24 ` 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=20220508163317.204673-1-elic@nvidia.com \
--to=elic@nvidia.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=si-wei.liu@oracle.com \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®