The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 v7 0/5] Show statistics for a vdpa device
Date: Tue, 17 May 2022 16:13:43 +0300	[thread overview]
Message-ID: <20220517131348.498421-1-elic@nvidia.com> (raw)

The following four 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 makes changes to locking scheme to use readers/writers
semaphore instead if mutex.

The fourth patch implements this for mlx5_vdpa which gives received
descriptors and completed descriptors information for all the
virtqueues.

The fifth patch changes reslock mutex to readers/writers semaphore to
achieve the same goal as done in vdpa core.

Eli Cohen (5):
  vdpa: Fix error logic in vdpa_nl_cmd_dev_get_doit
  vdpa: Add support for querying vendor statistics
  net/vdpa: Use readers/writers semaphore instead of mutex
  vdpa/mlx5: Add support for reading descriptor statistics
  vdpa/mlx5: Use readers/writers semaphore instead of mutex

v6 -> v7:
1. Add a new mlx5 patch to modify reslock from a mutex to rw_semaphore
2. Clean old comments
3. Move VDPA_ATTR_DEV_NET_CFG_MAX_VQP attribute insertion from mlx5 to
   vdpa core.

 drivers/vdpa/mlx5/core/mlx5_vdpa.h |   2 +
 drivers/vdpa/mlx5/net/mlx5_vnet.c  | 186 ++++++++++++++++++++---
 drivers/vdpa/vdpa.c                | 229 +++++++++++++++++++++++++----
 include/linux/mlx5/mlx5_ifc.h      |   1 +
 include/linux/mlx5/mlx5_ifc_vdpa.h |  39 +++++
 include/linux/vdpa.h               |   3 +
 include/uapi/linux/vdpa.h          |   6 +
 7 files changed, 414 insertions(+), 52 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-05-17 13:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 13:13 Eli Cohen [this message]
2022-05-17 13:13 ` [PATCH v7 1/5] vdpa: Fix error logic in vdpa_nl_cmd_dev_get_doit Eli Cohen
2022-05-17 13:13 ` [PATCH v7 2/5] vdpa: Add support for querying vendor statistics Eli Cohen
2022-05-18  1:03   ` Si-Wei Liu
2022-05-18  6:12     ` Eli Cohen
2022-05-17 13:13 ` [PATCH v7 3/5] net/vdpa: Use readers/writers semaphore instead of mutex Eli Cohen
2022-05-17 13:13 ` [PATCH v7 4/5] vdpa/mlx5: Add support for reading descriptor statistics Eli Cohen
2022-05-17 13:13 ` [PATCH v7 5/5] vdpa/mlx5: Use readers/writers semaphore instead of mutex Eli Cohen
2022-05-17 23:59   ` Si-Wei Liu

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=20220517131348.498421-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