From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: jcody@redhat.com, qemu-block@nongnu.org,
Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>,
Liu Yuan <namei.unix@gmail.com>
Subject: [Qemu-devel] [PATCH for-2.9 v3 0/5] Sheepdog cleanups
Date: Tue, 29 Nov 2016 12:32:40 +0100 [thread overview]
Message-ID: <20161129113245.32724-1-pbonzini@redhat.com> (raw)
Cleaning up the code and removing duplication makes it simpler to
later adapt it for the multiqueue work.
Tested against sheepdog 1.0. I also tested taking snapshots and reverting
to older snapshots, but the latter only worked with "dog vdi rollback".
Neither loadvm nor qemu-img worked for me.
Paolo
v1->v2: placate patchew
v2->v3: rebase
Paolo Bonzini (5):
sheepdog: remove unused cancellation support
sheepdog: reorganize coroutine flow
sheepdog: do not use BlockAIOCB
sheepdog: simplify inflight_aio_head management
sheepdog: reorganize check for overlapping requests
block/sheepdog.c | 289 ++++++++++++++++---------------------------------------
1 file changed, 83 insertions(+), 206 deletions(-)
--
2.9.3
next reply other threads:[~2016-11-29 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 11:32 Paolo Bonzini [this message]
2016-11-29 11:32 ` [Qemu-devel] [PATCH 1/5] sheepdog: remove unused cancellation support Paolo Bonzini
2016-11-29 11:32 ` [Qemu-devel] [PATCH 2/5] sheepdog: reorganize coroutine flow Paolo Bonzini
2016-11-29 11:32 ` [Qemu-devel] [PATCH 3/5] sheepdog: do not use BlockAIOCB Paolo Bonzini
2016-11-29 11:32 ` [Qemu-devel] [PATCH 4/5] sheepdog: simplify inflight_aio_head management Paolo Bonzini
2016-11-29 11:32 ` [Qemu-devel] [PATCH 5/5] sheepdog: reorganize check for overlapping requests Paolo Bonzini
2016-12-21 14:07 ` [Qemu-devel] [PATCH for-2.9 v3 0/5] Sheepdog cleanups Paolo Bonzini
2017-01-04 4:07 ` Jeff Cody
2017-01-04 11:42 ` Paolo Bonzini
2017-01-04 16:47 ` Jeff Cody
2017-01-31 1:48 ` Paolo Bonzini
2017-02-01 5:35 ` Jeff Cody
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=20161129113245.32724-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=jcody@redhat.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=namei.unix@gmail.com \
--cc=qemu-block@nongnu.org \
--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).