From: Stefan Hajnoczi <stefanha@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <famz@redhat.com>,
"Jeff Cody" <jcody@redhat.com>,
qemu-devel@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
"Benoît Canet" <benoit.canet@nodalink.com>
Subject: Re: [Qemu-devel] BlockBackend next steps
Date: Fri, 24 Oct 2014 13:28:05 +0100 [thread overview]
Message-ID: <20141024122805.GB2367@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <877fzrt1zu.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On Thu, Oct 23, 2014 at 02:16:37PM +0200, Markus Armbruster wrote:
> "Need BlockBackend" has been a recurring theme for a long time. It's
> finally on master now. Plenty of work left to do. Let's coordinate
> next steps to avoid duplicate work.
Great job. Thanks for sending this email. I haven't followed closely
and it helps me understand the current status.
Looks like many of these tasks can be done in parallel.
> * Convert block jobs
>
> We want to divorce jobs from the block layer, but since that'll
> probably take a while, lift them for now.
Breaking the 1:1 relationship between block jobs and BDS is nice
conceptually, but is there a concrete requirement? Unless there is a
use case that someone needs supported it's best to focus on more urgent
issues.
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-10-24 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 12:16 [Qemu-devel] BlockBackend next steps Markus Armbruster
2014-10-24 12:28 ` Stefan Hajnoczi [this message]
2014-10-24 12:56 ` Markus Armbruster
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=20141024122805.GB2367@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit.canet@nodalink.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).