Re: [Nbd] [PATCH v2 0/3] NBD Structured Read
- To: Eric Blake <eblake@...696...>
- Cc: nbd-general@lists.sourceforge.net, qemu-devel@...530...
- Subject: Re: [Nbd] [PATCH v2 0/3] NBD Structured Read
- From: Wouter Verhelst <w@...112...>
- Date: Wed, 30 Mar 2016 10:09:26 +0200
- Message-id: <20160330080926.GA3517@...3...>
- In-reply-to: <1459292460-6875-1-git-send-email-eblake@...696...>
- References: <1459173555-4890-1-git-send-email-eblake@...696...> <1459292460-6875-1-git-send-email-eblake@...696...>
Hi Eric,
On Tue, Mar 29, 2016 at 05:00:57PM -0600, Eric Blake wrote:
> I wrote this in parallel with Alex's strawman proposals, so I
> may have picked up on some of his ideas, while diverging in
> other places.
>
> Changes since v1: rebase, resend some pre-req patches, switch
> from global/client flag negotiation over to option negotiation,
> document a flags/type scheme in all structured replies, use
> ONLY structured replies in response to a structured read, make
> the server stream fully context-free (thanks to the type scheme),
> go into more details about error reporting by using two different
> structured errors (multiple errors each with offset, or single
> error with no offset).
>
> Eric Blake (2):
> doc: Mention proper use of handle
> doc: Propose Structured Read extension
>
> Pavel Borzenkov (1):
> NBD proto: add "Command flags" section
Thanks. 1 and 2 applied, 3 not yet (until resolution of discussion)
(not yet pushed yet, will do so later)
--
< 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
Reply to: