From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Eric Blake <eblake@redhat.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: [Qemu-devel] NBD BLOCK_STATUS
Date: Thu, 9 Nov 2017 15:42:31 +0300 [thread overview]
Message-ID: <37193dd7-a0fc-bfa6-3870-ecbcfefac4e5@virtuozzo.com> (raw)
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.
This is not really touched in spec, for example
"Change the set of active metadata contexts. Issuing this command
replaces all previously-set metadata contexts"
looks like lacking "for specified export" suffix. May be there are other
places.
--
Best regards,
Vladimir
next reply other threads:[~2017-11-09 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 12:42 Vladimir Sementsov-Ogievskiy [this message]
2017-11-10 16:06 ` [Qemu-devel] NBD BLOCK_STATUS Eric Blake
2017-11-10 16:51 ` Vladimir Sementsov-Ogievskiy
2017-11-13 14:13 ` Eric Blake
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=37193dd7-a0fc-bfa6-3870-ecbcfefac4e5@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=alex@alex.org.uk \
--cc=eblake@redhat.com \
--cc=nbd@other.debian.org \
--cc=qemu-devel@nongnu.org \
--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).