From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: devin122@gmail.com, Jes Sorensen <Jes.Sorensen@redhat.com>,
Jagane Sundar <jagane@sundar.org>, Dor Laor <dlaor@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
Feiran Zheng <famcool@gmail.com>,
Frediano Ziglio <freddy77@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] Block layer roadmap
Date: Thu, 28 Jul 2011 12:05:43 +0200 [thread overview]
Message-ID: <4E313477.2070905@redhat.com> (raw)
In-Reply-To: <CAJSP0QWqFaTd7Pv-Jo7fBE_eqGcgr7Hy4WQ+GcnwW+wGmZeKTA@mail.gmail.com>
Am 27.07.2011 14:37, schrieb Stefan Hajnoczi:
> Hi,
> Here is a list of block layer and storage changes that have been discussed. It
> is useful to have a roadmap of changes in order to avoid duplication, allow
> more developers to contribute, and to communicate the direction of storage in
> QEMU.
>
> I suggest we first do a braindump of all changes that have been discussed.
> Later we can discuss specific changes and if/when they fit into the roadmap -
> please don't jump into discussion about specific changes yet.
>
> Kevin: I hope this a useful starting point. Here are all the items
> that I am aware of:
>
> =Material for next QEMU release=
>
> Coroutines in the block layer [Kevin]
> * Programming model to simplify block drivers without blocking QEMU threads
>
> Generic copy-on-read [Stefan]
> * Populate image file to avoid fetching same block from backing file
> again later
>
> Generic image streaming [Stefan]
> * Make block_stream commands available for all image formats that
> support backing files
>
> Live block copy [Marcelo/Kevin/Stefan?]
> * Copy the contents of an image file while a guest is using it
>
> In-place qcow2 <-> qed conversion [Devin, GSoC 2011]:
> * Fast conversion between qcow2 and qed image formats without copy all data
>
> VMDK enhancements [Fam, GSoC 2011]
> * Implement latest VMDK specs to support modern image files
>
> Block I/O limits [Zhi Yong]
> * Resource control for guest I/O bandwidth/iops consumption
Another item that just came up on IRC again: Allow guests to toggle WCE,
so that we finally can get rid of the cache=writethrough default. We
should definitely get this done before 1.0.
Kevin
next prev parent reply other threads:[~2011-07-28 10:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 12:37 [Qemu-devel] Block layer roadmap Stefan Hajnoczi
2011-07-27 12:50 ` Anthony Liguori
2011-07-28 10:05 ` Kevin Wolf [this message]
2011-07-28 12:08 ` Christoph Hellwig
2011-07-28 12:29 ` Kevin Wolf
2011-07-28 10:52 ` Stefan Hajnoczi
2011-07-28 12:09 ` Christoph Hellwig
2011-07-28 12:15 ` Frediano Ziglio
2011-07-28 12:16 ` Christoph Hellwig
2011-07-28 12:35 ` Kevin Wolf
2011-07-28 12:54 ` Stefan Hajnoczi
2011-07-28 13:10 ` Kevin Wolf
2011-07-28 13:11 ` Stefan Hajnoczi
2011-07-28 12:52 ` Anthony Liguori
2011-07-29 12:35 ` Stefan Hajnoczi
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=4E313477.2070905@redhat.com \
--to=kwolf@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=armbru@redhat.com \
--cc=devin122@gmail.com \
--cc=dlaor@redhat.com \
--cc=famcool@gmail.com \
--cc=freddy77@gmail.com \
--cc=jagane@sundar.org \
--cc=pbonzini@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).