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: Thu, 12 Jan 2017 10:05:28 +0300 [thread overview]
Message-ID: <dcaf043a-9e76-3be2-1740-e90085928f6a@virtuozzo.com> (raw)
In-Reply-To: <6986E12E-AE0A-4502-BB43-77C4E83C9DC4@alex.org.uk>
11.01.2017 22:00, Alex Bligh wrote:
>> On 11 Jan 2017, at 15:31, Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> wrote:
>>
>>>>> If an error occurs, the server SHOULD set the appropriate error code in the error field of an error chunk. However, if the error does not involve invalid usage (such as a request beyond the bounds of the file), a server MAY reply with a single block status descriptor with length matching the requested length, and status of 0 rather than reporting the error.
>> - single block status descriptor for each context? Isn't it implementation defined? Or we finally decided to force 0 status to be safe default for all contexts? If it is so, it would be better to describe this separately. However, personally, I'd prefer to not define contexts internal semantics at all.
> I think this is Wouter's wording, but I think 'a status appropriate to the context' would be better. Each context then needs to define what that is. Either that or 'the context's default status' and that should be in the definition of the context.
>
Yes this is better. But is it actually needed to force contexts have
some safe default? If context wants it may define such default without
this requirement.. So, should it be requirement at all?
--
Best regards,
Vladimir
next prev parent reply other threads:[~2017-01-12 7:05 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
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 [this message]
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=dcaf043a-9e76-3be2-1740-e90085928f6a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.