[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Nbd] [PATCH v5] doc: Add NBD_CMD_BLOCK_STATUS extensio
From: |
Alex Bligh |
Subject: |
Re: [Qemu-devel] [Nbd] [PATCH v5] doc: Add NBD_CMD_BLOCK_STATUS extension (part 2) |
Date: |
Tue, 13 Dec 2016 14:12:48 +0000 |
> On 12 Dec 2016, at 20:43, Wouter Verhelst <address@hidden> wrote:
>
> +- `NBD_OPT_SET_META_CONTEXT` (11)
> +
> + Change the set of active metadata contexts. Issuing this command
> + replaces all previously-set metadata contexts; clients must ensure
> + that all metadata contexts they're interested in are selected with
> + the final query that they sent.
> +
> + Data:
> + - 32 bits, length of query
> + - String, query to select metadata contexts. The syntax of this
> + query is implementation-defined, except that it MUST start with a
> + namespace. This namespace may be one of the following:
> + - `base:`, for metadata contexts defined by this document;
> + - `nbd-server:`, for metadata contexts defined by the
> + implementation that accompanies this document (none
> + currently);
> + - `x-*:`, where `*` can be replaced by any random string not
> + containing colons, for local experiments. This SHOULD NOT be
> + used by metadata contexts that are expected to e widely used.
> + - third-party implementations can register additional
> + namespaces by simple request to the mailinglist.
Surely also we need to specify multiple queries?
--
Alex Bligh
signature.asc
Description: Message signed with OpenPGP using GPGMail
Re: [Qemu-devel] [Nbd] [PATCH v5] doc: Add NBD_CMD_BLOCK_STATUS extension (part 2),
Alex Bligh <=