From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Dor Laor <dlaor@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
Adam Litke <agl@us.ibm.com>
Subject: Re: [Qemu-devel] live block copy/stream/snapshot discussion
Date: Thu, 14 Jul 2011 11:00:40 +0100 [thread overview]
Message-ID: <CAJSP0QXOA-qvWegnfYOHS7BnUNDS811r467ogN825ZyDJ0Hf1A@mail.gmail.com> (raw)
In-Reply-To: <4E1EBD24.9090308@redhat.com>
On Thu, Jul 14, 2011 at 10:55 AM, Kevin Wolf <kwolf@redhat.com> wrote:
> Am 14.07.2011 11:39, schrieb Stefan Hajnoczi:
>> Events:
>>
>> On completion the BLOCK_STREAM_COMPLETED event is raised with the following
>> fields:
>>
>> - device: device name (json-string)
>> - len: size of the device, in bytes (json-int)
>> - offset: last offset of completed I/O, in bytes (json-int)
>> - error: error message (json-string, only on error)
>>
>> The completion event is raised both on success and on failure.
>
> Why do len/offset matter in a completion event?
For completeness. You could see it as telling you how much progress
was made before an error occurred. In the success case offset will
always be equal to len. But in the error case you get the last
completed progress before error, which could be useful (for example if
you weren't polling but want to display "Streaming virtio-blk0 failed
at 33%").
Stefan
next prev parent reply other threads:[~2011-07-14 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 14:17 [Qemu-devel] live block copy/stream/snapshot discussion Dor Laor
2011-07-11 12:54 ` Stefan Hajnoczi
2011-07-11 14:47 ` Stefan Hajnoczi
2011-07-11 16:32 ` Marcelo Tosatti
2011-07-12 8:06 ` Kevin Wolf
2011-07-12 15:45 ` Stefan Hajnoczi
2011-07-12 16:10 ` Kevin Wolf
2011-07-13 9:51 ` Stefan Hajnoczi
2011-07-14 9:39 ` Stefan Hajnoczi
2011-07-14 9:55 ` Kevin Wolf
2011-07-14 10:00 ` Stefan Hajnoczi [this message]
2011-07-14 10:07 ` Kevin Wolf
2011-07-12 17:47 ` Adam Litke
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=CAJSP0QXOA-qvWegnfYOHS7BnUNDS811r467ogN825ZyDJ0Hf1A@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=agl@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=dlaor@redhat.com \
--cc=kwolf@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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.