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 v2 0/2] Show statistics for a vdpa device
Date: Tue, 12 Apr 2022 16:04:00 +0300 [thread overview]
Message-ID: <20220412130402.46945-1-elic@nvidia.com> (raw)
The following two patch series adds support to read vendor statistics
for a vdpa device.
The first patch lays the ground to allow an upstream driver to provide
statistics in the form of an attribute name/attribute value pairs.
The second patch implements this for mlx5_vdpa which gives received
descriptors and completed descriptors information for all the
virtqueues.
v1->v2:
Return negotiated features and max virtqueue pairs in each stats record
to aid userspace in determining if this is a data or control virtqueue.
Eli Cohen (2):
vdpa: Add support for querying vendor statistics
vdpa/mlx5: Add support for reading descriptor statistics
drivers/vdpa/mlx5/core/mlx5_vdpa.h | 2 +
drivers/vdpa/mlx5/net/mlx5_vnet.c | 165 +++++++++++++++++++++++++++++
drivers/vdpa/vdpa.c | 129 ++++++++++++++++++++++
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, 347 insertions(+)
--
2.35.1
next reply other threads:[~2022-04-12 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 13:04 Eli Cohen [this message]
2022-04-12 13:04 ` [PATCH v2 1/2] vdpa: Add support for querying vendor statistics Eli Cohen
2022-04-12 16:28 ` kernel test robot
2022-04-12 13:04 ` [PATCH v2 2/2] vdpa/mlx5: Add support for reading descriptor statistics Eli Cohen
2022-04-18 19:03 ` kernel test robot
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=20220412130402.46945-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