virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Zhu Lingshan <lingshan.zhu@intel.com>
Cc: jasowang@redhat.com, virtualization@lists.linux.dev
Subject: Re: [PATCH 00/10] vDPA: allow userspace query virito-block device
Date: Tue, 19 Mar 2024 02:39:56 -0400	[thread overview]
Message-ID: <20240319023840-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240218185606.13509-1-lingshan.zhu@intel.com>

On Mon, Feb 19, 2024 at 02:55:56AM +0800, Zhu Lingshan wrote:
> This series allows the user space applications query vDPA virtio-block
> device inforamtion.
> 
> testing on vdpa_sim_blk, iproute2 output:
> sudo ./vdpa/vdpa dev config show -jp vdpa_blk0
> {
>     "config": {
>         "vdpa_blk0": {
>             "capacity": 262144,
>             "segment size": 4096,
>             "block size": 512,
>             "max segments in a request": 32,
>             "num of queues": 1,
>             "logical blocks per physical block (log2)": 0,
>             "offset of first aligned logical block": 0,
>             "minimum io size": 1,
>             "optimal io size": 1,
>             "maximum discard sectors for a segment": 4294967295,
>             "max discard segments in a command": 1,
>             "discard sector alignment": 512,
>             "max write zeros sectors in a segment": 4294967295,
>             "max write zero segments": 1,
>             "read only": false,
>             "flush command support": true
>         }
>     }
> }
> 
> Please help review
> 
> Thanks
> Zhu Lingshan

It's been in my tree for a while so it will be in the next pull,
but going forward Jason I'd like to know what kind of
timeline do you have in mind for reviewing vdpa patches?

> Zhu Lingshan (10):
>   vDPA: report virtio-block capacity to user space
>   vDPA: report virtio-block max segment size to user space
>   vDPA: report virtio-block block-size to user space
>   vDPA: report virtio-block max segments in a request to user space
>   vDPA: report virtio-block MQ info to user space
>   vDPA: report virtio-block topology info to user space
>   vDPA: report virtio-block discarding configuration to user space
>   vDPA: report virtio-block write zeroes configuration to user space
>   vDPA: report virtio-block read-only info to user space
>   vDPA: report virtio-blk flush info to user space
> 
>  drivers/vdpa/vdpa.c       | 212 ++++++++++++++++++++++++++++++++++++++
>  include/linux/vdpa.h      |   1 +
>  include/uapi/linux/vdpa.h |  17 +++
>  3 files changed, 230 insertions(+)
> 
> -- 
> 2.39.3


  parent reply	other threads:[~2024-03-19  6:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 18:55 [PATCH 00/10] vDPA: allow userspace query virito-block device Zhu Lingshan
2024-02-18 18:55 ` [PATCH 01/10] vDPA: report virtio-block capacity to user space Zhu Lingshan
2024-03-19 16:43   ` Stefano Garzarella
2024-02-18 18:55 ` [PATCH 02/10] vDPA: report virtio-block max segment size " Zhu Lingshan
2024-03-19 16:04   ` Stefano Garzarella
2024-03-29 14:48     ` Zhu, Lingshan
2024-03-31 20:03       ` Michael S. Tsirkin
2024-02-18 18:55 ` [PATCH 03/10] vDPA: report virtio-block block-size " Zhu Lingshan
2024-03-19 16:43   ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 04/10] vDPA: report virtio-block max segments in a request " Zhu Lingshan
2024-03-19 16:43   ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 05/10] vDPA: report virtio-block MQ info " Zhu Lingshan
2024-03-19 16:44   ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 06/10] vDPA: report virtio-block topology " Zhu Lingshan
2024-03-19 16:44   ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 07/10] vDPA: report virtio-block discarding configuration " Zhu Lingshan
2024-03-19 16:44   ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 08/10] vDPA: report virtio-block write zeroes " Zhu Lingshan
2024-03-19 16:36   ` Stefano Garzarella
2024-03-19 17:02     ` Michael S. Tsirkin
2024-03-19 17:08       ` Stefano Garzarella
2024-03-19 17:57         ` Michael S. Tsirkin
2024-02-18 18:56 ` [PATCH 09/10] vDPA: report virtio-block read-only info " Zhu Lingshan
2024-03-19 16:40   ` Stefano Garzarella
2024-04-09  8:37     ` Zhu, Lingshan
2024-05-03 12:18       ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 10/10] vDPA: report virtio-blk flush " Zhu Lingshan
2024-03-19 16:42   ` Stefano Garzarella
2024-03-19  6:39 ` Michael S. Tsirkin [this message]
2024-03-20  3:30   ` [PATCH 00/10] vDPA: allow userspace query virito-block device Jason Wang
2024-03-20  7:00     ` Michael S. Tsirkin
2024-03-19 16:49 ` Stefano Garzarella
2024-03-20 10:31   ` Zhu, Lingshan
2024-03-20 10:53     ` Stefano Garzarella

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=20240319023840-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lingshan.zhu@intel.com \
    --cc=virtualization@lists.linux.dev \
    /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).