[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Nbd] [PATCH 3/3] NBD proto: add "Command flags" sectio
Re: [Qemu-devel] [Nbd] [PATCH 3/3] NBD proto: add "Command flags" section
Tue, 29 Mar 2016 09:34:37 +0200
On Mon, Mar 28, 2016 at 07:45:27AM -0600, Eric Blake wrote:
> On 03/28/2016 04:43 AM, Denis V. Lunev wrote:
> > From: Pavel Borzenkov <address@hidden>
> > Add separate "Command flags" section to make it clear which flags are
> > currently defined by the protocol.
> > Signed-off-by: Pavel Borzenkov <address@hidden>
> > Reviewed-by: Roman Kagan <address@hidden>
> > Signed-off-by: Denis V. Lunev <address@hidden>
> > CC: Wouter Verhelst <address@hidden>
> > CC: Eric Blake <address@hidden>
> > CC: Alex Bligh <address@hidden>
> > ---
> > doc/proto.md | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> > diff --git a/doc/proto.md b/doc/proto.md
> > index 036d6d9..662f741 100644
> > --- a/doc/proto.md
> > +++ b/doc/proto.md
> > @@ -485,6 +485,16 @@ The following request types exist:
> > Currently one such message is known: `NBD_CMD_CACHE`, with type set to
> > 5, implemented by xnbd.
> > +#### Command flags
> > +
> > +This field of 16 bits is sent by the client with every request and provides
> > +additional information to the server to execute the command. Refer to
> > +aforementioned "Request types" section for information about the flags
> s/aforementioned "Request types" section/the "Request types" section above/
> > +supported by particular commands.
> > +
> > +- bit 0, `NBD_CMD_FLAG_FUA`; should be set to 1 if the client requires
> > + "Force Unit Access" mode of operation
> Trailing dot? Should you also mention which command(s) it is valid
> with? (NBD_CMD_WRITE for now, until other extension commands are added)
> It might also be worth mentioning that the flag should not be sent
> unless export flags included NBD_FLAG_SEND_FUA.
> > +
> > #### Error values
> > The error values are used for the error field in the reply message.
Yes, I agree that these are all (typographical, but still) improvements.
If you can update with that, I'll happily apply that.
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
people in the world who think they really understand all of its rules,
and pretty much all of them are just lying to themselves too.
-- #debian-devel, OFTC, 2016-02-12