qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	Wouter Verhelst <w@uter.be>, Alex Bligh <alex@alex.org.uk>,
	nbd list <nbd@other.debian.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] NBD BLOCK_STATUS
Date: Mon, 13 Nov 2017 08:13:16 -0600	[thread overview]
Message-ID: <f109edd5-ef86-ff6d-c242-e0731d919c77@redhat.com> (raw)
In-Reply-To: <608ba1f1-38b3-7312-e27b-8a62b197d53e@virtuozzo.com>

[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]

On 11/10/2017 10:51 AM, Vladimir Sementsov-Ogievskiy wrote:
> 10.11.2017 19:06, Eric Blake wrote:
>> On 11/09/2017 06:42 AM, Vladimir Sementsov-Ogievskiy wrote:
>>> Hi!
>>>
>>> Interesting fact: list/set_meta_context options are per-export,
>>> so, in the server we should keep context selection per client per
>>> export.
>>>
>>> And it is possible for client to set contexts for one export and than
>>> proceed
>>> to transmission phase with another one.
>> However, we also documented in the spec that
>>
>> +    A client MUST NOT send `NBD_CMD_BLOCK_STATUS` unless
>> +    within the negotiation phase it sent `NBD_OPT_SET_META_CONTEXT`
>> +    at least once, and the final time it was sent, it referred
>> +    to the export name that was ultimately selected, the server
>> +    responded without an error, and returned at least one metadata
>> +    context.
> 
> I've missed this, then it's OK.
> 
> maybe "ultimately selected for transmission phase" would be a bit better.

Sure, I'll queue that up for my next round of doc tweaks.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

      reply	other threads:[~2017-11-13 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 12:42 [Qemu-devel] NBD BLOCK_STATUS Vladimir Sementsov-Ogievskiy
2017-11-10 16:06 ` Eric Blake
2017-11-10 16:51   ` Vladimir Sementsov-Ogievskiy
2017-11-13 14:13     ` Eric Blake [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=f109edd5-ef86-ff6d-c242-e0731d919c77@redhat.com \
    --to=eblake@redhat.com \
    --cc=alex@alex.org.uk \
    --cc=nbd@other.debian.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.com \
    --cc=w@uter.be \
    /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).