All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
	virtio-dev@lists.oasis-open.org,
	Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [virtio-dev] [PATCH] virtio-blk: clarify semantics of multi-segment discard/write zeroes commands
Date: Tue, 26 Feb 2019 14:51:04 -0500	[thread overview]
Message-ID: <20190226145002-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190226174416.GA2339@stefanha-x1.localdomain>

On Tue, Feb 26, 2019 at 05:44:16PM +0000, Stefan Hajnoczi wrote:
> On Tue, Feb 26, 2019 at 06:09:03PM +0100, Cornelia Huck wrote:
> > On Tue, 26 Feb 2019 16:25:53 +0000
> > Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > 
> > > Describe the failure case and maximum number of segments in a
> > > multi-segment discard/write zeroes command.
> > > 
> > > Fixes: https://github.com/oasis-tcs/virtio-spec/issues/34
> > > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > ---
> > > I would like to request a vote on this.
> > 
> > Only one minor nit from me, below.
> > 
> > > 
> > >  content.tex | 23 +++++++++++++++++++++--
> > >  1 file changed, 21 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/content.tex b/content.tex
> > > index c5fdc34..7bfcc78 100644
> > > --- a/content.tex
> > > +++ b/content.tex
> > > @@ -3967,8 +3967,10 @@ read from the block device (in multiples of 512 bytes).  VIRTIO_BLK_T_OUT
> > >  requests write the contents of \field{data} to the block device (in multiples
> > >  of 512 bytes).
> > >  
> > > -The \field{data} used for discard or write zeroes command is described
> > > -by one or more virtio_blk_discard_write_zeroes structs:
> > > +The \field{data} used for discard or write zeroes commands consists of one or
> > > +more segments.  The maximum number of segments is \field{max_discard_seg} for
> > > +discard commands and \field{max_write_zeroes_seg} for write zeroes commands.
> > > +Each segment is of form:
> > 
> > Maybe s/of form/of the form/ ?
> 
> I wanted to stay consistent with the existing text above it:
> 
>   The driver queues requests to the virtqueue, and they are used by
>   the device (not necessarily in order). Each request is of form:
> 
>   ...



OK so I will cancel the vote on this version for now?

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


      parent reply	other threads:[~2019-02-26 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 16:25 [virtio-dev] [PATCH] virtio-blk: clarify semantics of multi-segment discard/write zeroes commands Stefan Hajnoczi
2019-02-26 17:09 ` Cornelia Huck
2019-02-26 17:44   ` Cornelia Huck
2019-02-26 17:44   ` Stefan Hajnoczi
2019-02-26 17:45     ` Cornelia Huck
2019-02-26 19:54       ` Stefan Hajnoczi
2019-02-26 19:51     ` Michael S. Tsirkin [this message]

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=20190226145002-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-dev@lists.oasis-open.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.