virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Zhu Lingshan <lingshan.zhu@intel.com>,
	jasowang@redhat.com, virtualization@lists.linux.dev
Subject: Re: [PATCH 08/10] vDPA: report virtio-block write zeroes configuration to user space
Date: Tue, 19 Mar 2024 13:57:24 -0400	[thread overview]
Message-ID: <20240319135639-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <disso3ouyi3wrxqx5fa2v2kiaub3lsfdfwhhf3ghpf56oegczj@gwzaojtdoln5>

On Tue, Mar 19, 2024 at 06:08:13PM +0100, Stefano Garzarella wrote:
> On Tue, Mar 19, 2024 at 01:02:21PM -0400, Michael S. Tsirkin wrote:
> > On Tue, Mar 19, 2024 at 05:36:01PM +0100, Stefano Garzarella wrote:
> > > On Mon, Feb 19, 2024 at 02:56:04AM +0800, Zhu Lingshan wrote:
> > > > This commits reports write zeroes configuration of
> > > > virtio-block devices to user space, includes:
> > > > 1)maximum write zeroes sectors size
> > > > 2)maximum write zeroes segment number
> > > >
> > > > Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
> > > > ---
> > > > drivers/vdpa/vdpa.c       | 23 +++++++++++++++++++++++
> > > > include/uapi/linux/vdpa.h |  2 ++
> > > > 2 files changed, 25 insertions(+)
> > > >
> > > > diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c
> > > > index bf3fa90908a7..adbcbc7b18b2 100644
> > > > --- a/drivers/vdpa/vdpa.c
> > > > +++ b/drivers/vdpa/vdpa.c
> > > > @@ -1064,6 +1064,26 @@ static int vdpa_dev_blk_discard_config_fill(struct sk_buff *msg, u64 features,
> > > > 	return 0;
> > > > }
> > > >
> > > > +static int
> > > > +vdpa_dev_blk_write_zeroes_config_fill(struct sk_buff *msg, u64 features,
> > > > +				     const struct virtio_blk_config *config)
> > > > +{
> > > > +	u32 val_u32;
> > > > +
> > > > +	if ((features & BIT_ULL(VIRTIO_BLK_F_WRITE_ZEROES)) == 0)
> > > > +		return 0;
> > > > +
> > > > +	val_u32 = __virtio32_to_cpu(true, config->max_write_zeroes_sectors);
> > > > +	if (nla_put_u32(msg, VDPA_ATTR_DEV_BLK_CFG_MAX_WRITE_ZEROES_SEC, val_u32))
> > > > +		return -EMSGSIZE;
> > > > +
> > > > +	val_u32 = __virtio32_to_cpu(true, config->max_write_zeroes_seg);
> > > > +	if (nla_put_u32(msg, VDPA_ATTR_DEV_BLK_CFG_MAX_WRITE_ZEROES_SEG, val_u32))
> > > > +		return -EMSGSIZE;
> > > 
> > > Should we cover also `config->write_zeroes_may_unmap` ?
> > 
> > 
> > This review came too late I applied the patch. Generally
> > if I don't see any response in about
> > a week I assume there is not interest.
> 
> Ooops, sorry about that! I should add me as a reviewer for vDPA
> otherwise lately it's hard for me to monitor patches :-(
> 
> BTW, some comments can be resolved with later patches if you think it
> makes sense to resolve them.
> 
> Thanks,
> Stefano

Sure. Once the pressure to merge the patch is gone not everyone
will bother though, it might be easier for you to send the patch on top.

-- 
MST


  reply	other threads:[~2024-03-19 17:57 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 [this message]
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 ` [PATCH 00/10] vDPA: allow userspace query virito-block device Michael S. Tsirkin
2024-03-20  3:30   ` 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=20240319135639-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lingshan.zhu@intel.com \
    --cc=sgarzare@redhat.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).