From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: Wouter Verhelst <w@uter.be>,
"nbd-general@lists.sourceforge.net"
<nbd-general@lists.sourceforge.net>,
Kevin Wolf <kwolf@redhat.com>,
"Stefan stefanha@redhat. com" <stefanha@redhat.com>,
John Snow <jsnow@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Pavel Borzenkov <pborzenkov@virtuozzo.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Markus Pargmann <mpa@pengutronix.de>,
"Denis V . Lunev" <den@openvz.org>
Subject: Re: [Qemu-devel] [PATCH] Further tidy-up on block status
Date: Wed, 14 Dec 2016 20:05:44 +0300 [thread overview]
Message-ID: <5e9150ed-2127-f2e8-f9db-a514e8f0ddf8@virtuozzo.com> (raw)
In-Reply-To: <6D1B30FC-FD7E-474C-A8E3-FD87E7AA1364@alex.org.uk>
14.12.2016 19:38, Alex Bligh wrote:
> Vladimir,
>
>>> +non-zero number of metadata contexts during negotiation. Servers SHOULD
>>> +reply to clients sending `NBD_CMD_BLOCK_STATUS without
>> backquote
> Fixed
>
>>> + If zero queries are sent, then the server MUST return all
>>> + the metadata contexts it knows about.
>> I think that 'all .. it knows about' is too much. What about 'return all available ..'? Anyway 'all ... it knows about' actually equals to 'all ... it wants'. There may be some private, or unrelated contexts, for example..
> This was not my wording, but I've changed it anyway to:
>
> If zero queries are sent, then the server MUST return all
> the metadata contexts that are available to the client to select
> on the given export with `NBD_OPT_SET_META_CONTEXT`.
>
> I think if they are available to select, we should list them. Thanks
> also for reminding me to document why I put the export name into the
> _LIST_ data (as it is for _SET_).
>
> However, this raises another question. Wouter deliberately made the
> query format freeform so that you could e.g. set a context like:
>
> backup:modtime>201612081034
>
> which might (in theory) return a list of blocks which are newer than
> the given timestamp. It would clearly be impossible to return all such
> contexts. I wonder if we should carve out an exception here.
>
Interesting. Even query 'backup:modtime>*' would be a problem, not only
empty query list.
Actually, we do not need to 'list contexts', as it is about management,
not about data transfer. We only need a way to check, that particular
query selects all needed contexts and no others. Just to be sure that we
are know, what we will select by NBD_OPT_SET_META_CONTEXT with _same_ query.
So, I suggest just to say, that _LIST_ can return error if too much
contexts are selected.|And same should be done for _SET_. And it should
be documented that this result of query (list or error) should be equal
for these two commands.
|
--
Best regards,
Vladimir
next prev parent reply other threads:[~2016-12-14 17:06 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 15:08 [Qemu-devel] [PATCH] Further tidy-up on block status Alex Bligh
2016-12-14 16:25 ` Vladimir Sementsov-Ogievskiy
2016-12-14 16:38 ` Alex Bligh
2016-12-14 17:05 ` Vladimir Sementsov-Ogievskiy [this message]
2016-12-14 17:36 ` Alex Bligh
2016-12-14 17:55 ` Vladimir Sementsov-Ogievskiy
2016-12-14 18:13 ` [Qemu-devel] [Nbd] " Wouter Verhelst
2016-12-14 18:18 ` Alex Bligh
2016-12-14 18:49 ` Wouter Verhelst
2016-12-14 19:01 ` Alex Bligh
2016-12-14 20:10 ` Wouter Verhelst
2016-12-26 15:57 ` Vladimir Sementsov-Ogievskiy
2016-12-29 16:08 ` Alex Bligh
2016-12-29 16:35 ` Vladimir Sementsov-Ogievskiy
2016-12-14 18:51 ` Alex Bligh
2016-12-14 20:18 ` Wouter Verhelst
2016-12-15 10:04 ` Alex Bligh
2016-12-15 15:03 ` Wouter Verhelst
2016-12-15 16:32 ` Alex Bligh
2016-12-15 16:49 ` Wouter Verhelst
2016-12-15 17:34 ` Alex Bligh
2016-12-16 15:52 ` Wouter Verhelst
2016-12-16 16:25 ` Alex Bligh
2016-12-17 8:34 ` Wouter Verhelst
2016-12-17 9:41 ` Alex Bligh
2016-12-14 18:17 ` [Qemu-devel] " Alex Bligh
2016-12-26 14:52 ` Vladimir Sementsov-Ogievskiy
2016-12-28 0:18 ` [Qemu-devel] [Nbd] " Wouter Verhelst
2016-12-29 16:04 ` Alex Bligh
2016-12-29 16:28 ` Vladimir Sementsov-Ogievskiy
2016-12-14 16:58 ` [Qemu-devel] " Eric Blake
2016-12-14 17:03 ` Alex Bligh
2016-12-14 17:09 ` [Qemu-devel] [Nbd] " Wouter Verhelst
2016-12-14 17:33 ` Vladimir Sementsov-Ogievskiy
2016-12-14 17:39 ` Alex Bligh
2016-12-14 20:47 ` John Snow
2018-05-03 16:18 ` Eric Blake
2018-05-03 17:26 ` Eric Blake
2018-05-04 6:40 ` Wouter Verhelst
2016-12-27 14:09 ` [Qemu-devel] " Vladimir Sementsov-Ogievskiy
2016-12-27 15:56 ` Eric Blake
2016-12-29 16:14 ` Alex Bligh
2017-01-11 15:31 ` Vladimir Sementsov-Ogievskiy
2017-01-11 19:00 ` Alex Bligh
2017-01-12 7:05 ` Vladimir Sementsov-Ogievskiy
2017-01-12 13:11 ` Alex Bligh
2017-01-13 9:48 ` Vladimir Sementsov-Ogievskiy
2017-01-13 10:29 ` Alex Bligh
2017-01-16 12:26 ` Vladimir Sementsov-Ogievskiy
2017-01-12 11:43 ` Vladimir Sementsov-Ogievskiy
2017-01-12 13:16 ` Alex Bligh
2017-01-20 17:04 ` Vladimir Sementsov-Ogievskiy
2017-01-20 18:00 ` Alex Bligh
2017-01-20 19:35 ` Eric Blake
2017-01-21 12:25 ` [Qemu-devel] [Nbd] " Wouter Verhelst
2018-02-16 12:35 ` Eric Blake
2018-02-16 13:53 ` Vladimir Sementsov-Ogievskiy
2018-02-16 16:10 ` Eric Blake
2018-02-28 13:08 ` Wouter Verhelst
2018-02-28 20:26 ` Eric Blake
2018-02-28 20:29 ` Eric Blake
2018-03-01 9:54 ` Vladimir Sementsov-Ogievskiy
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=5e9150ed-2127-f2e8-f9db-a514e8f0ddf8@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=alex@alex.org.uk \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mpa@pengutronix.de \
--cc=nbd-general@lists.sourceforge.net \
--cc=pbonzini@redhat.com \
--cc=pborzenkov@virtuozzo.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).