From: Jeff Cody <jcody@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Benoît Canet" <benoit.canet@irqsave.net>,
"Fam Zheng" <famz@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Max Reitz" <mreitz@redhat.com>
Subject: Re: [Qemu-devel] Block layer meeting notes from June 10/11
Date: Fri, 13 Jun 2014 09:53:55 -0400 [thread overview]
Message-ID: <20140613135355.GB20898@localhost.localdomain> (raw)
In-Reply-To: <CAJSP0QU1L=VmuQM8ZxsWoNf3dpukhdDrExk7_3e9T1HaZyXm8A@mail.gmail.com>
On Fri, Jun 13, 2014 at 09:28:28PM +0800, Stefan Hajnoczi wrote:
>
<snip>
> * Mutual exclusion of operations/background jobs (bs->in_use / BlockOpType)
> * Streaming in two different parts of the backing chain - allowed?
> (Benoît though that not, but does anything break?)
> * Does streaming only require that streamed images stay read-only
> (i.e. backing chain segment on which the operation is performed)
> * Live commit in the opposite direction at the same time?
>
> Action:
> * Draw up matrix of operations (mirror, stream, resize, etc)
> * Make op blocker mechanism use matrix as data instead of code
> (define an array)
> * Enforce that new QMP/QAPI commands and block jobs add themselves to
> the matrix
> * Recursively add blockers to child nodes (driver method?) [Benoit]
>
Benoit, you have quite a few items on your list - would it be useful
if I worked on this? It would dovetail nicely with the node-name
commit/stream patches.
Thanks,
Jeff
next prev parent reply other threads:[~2014-06-13 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 13:28 [Qemu-devel] Block layer meeting notes from June 10/11 Stefan Hajnoczi
2014-06-13 13:40 ` Jeff Cody
2014-06-13 13:53 ` Jeff Cody [this message]
2014-06-13 14:17 ` Benoît Canet
2014-06-13 14:49 ` Benoît Canet
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=20140613135355.GB20898@localhost.localdomain \
--to=jcody@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).