From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: [Qemu-devel] [RFC PATCH v2 0/4] block-queue: Delay and batch metadata writes
Date: Fri, 5 Nov 2010 19:38:23 +0100 [thread overview]
Message-ID: <1288982307-30559-1-git-send-email-kwolf@redhat.com> (raw)
Still not quite there, but should be a bit more correct than the first RFC.
I still need to add proper error handling, the rest of block-queue itself
should be fairly complete. With respect to error handling, IDE, virtio-blk and
scsi-disk can deal with failed bdrv_(aio_)flush now, so just failing the next
flush seems to be a viable option now.
The integration into block.c and qcow2 is only a preliminary hack for now and
is going to be replaced.
Kevin Wolf (4):
block: Fake a bdrv_aio_pwrite
Add block-queue
Test cases for block-queue
qcow2: Use block-queue
Makefile | 1 +
Makefile.objs | 2 +-
block-queue.c | 625 ++++++++++++++++++++++++++++++++++++++++++++++++
block-queue.h | 49 ++++
block.c | 30 +++
block.h | 2 +
block/qcow2-cluster.c | 39 ++--
block/qcow2-refcount.c | 62 +++---
block/qcow2.c | 18 ++-
block/qcow2.h | 4 +
check-block-queue.c | 402 +++++++++++++++++++++++++++++++
11 files changed, 1182 insertions(+), 52 deletions(-)
create mode 100644 block-queue.c
create mode 100644 block-queue.h
create mode 100644 check-block-queue.c
--
1.7.2.3
next reply other threads:[~2010-11-05 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 18:38 Kevin Wolf [this message]
2010-11-05 18:38 ` [Qemu-devel] [RFC PATCH v2 1/4] block: Fake a bdrv_aio_pwrite Kevin Wolf
2010-11-05 18:38 ` [Qemu-devel] [RFC PATCH v2 2/4] Add block-queue Kevin Wolf
2010-11-17 12:43 ` Stefan Hajnoczi
2010-11-17 13:41 ` Kevin Wolf
2010-11-17 16:23 ` Stefan Hajnoczi
2010-11-18 9:46 ` Kevin Wolf
2010-11-17 16:24 ` Stefan Hajnoczi
2010-11-05 18:38 ` [Qemu-devel] [RFC PATCH v2 3/4] Test cases for block-queue Kevin Wolf
2010-11-05 18:38 ` [Qemu-devel] [RFC PATCH v2 4/4] qcow2: Use block-queue Kevin Wolf
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=1288982307-30559-1-git-send-email-kwolf@redhat.com \
--to=kwolf@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).