qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org,
	Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>,
	Liu Yuan <namei.unix@gmail.com>,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.9 v3 0/5] Sheepdog cleanups
Date: Wed, 4 Jan 2017 11:47:52 -0500	[thread overview]
Message-ID: <20170104164752.GC30425@localhost.localdomain> (raw)
In-Reply-To: <d4ad8370-cbcb-e4fd-b89d-5d7cb63569e6@redhat.com>

On Wed, Jan 04, 2017 at 12:42:53PM +0100, Paolo Bonzini wrote:
> 
> 
> On 04/01/2017 05:07, Jeff Cody wrote:
> > On Wed, Dec 21, 2016 at 03:07:07PM +0100, Paolo Bonzini wrote:
> >>
> >>
> >> On 29/11/2016 12:32, Paolo Bonzini wrote:
> >>> 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.8 is now out, so ping.
> >>
> > 
> > I don't have a functional sheepdog setup at the moment; have you tested
> > these patches, or should I set up a test rig for them? (I am guessing I
> > should do the latter; either way, I'll pull the patches in once I or someone
> > else has tested them).
> 
> Yes, I have tested them.  Fedora's sheepdog package is fubar right now.
> I've built an updated one and asked for ownership but haven't had any
> answer yet.
> 
> Paolo

Great, thanks.

Applied to my block branch:

git://github.com/codyprime/qemu-kvm-jtc.git block

-Jeff

  reply	other threads:[~2017-01-04 16:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 11:32 [Qemu-devel] [PATCH for-2.9 v3 0/5] Sheepdog cleanups Paolo Bonzini
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 [this message]
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=20170104164752.GC30425@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=mitake.hitoshi@lab.ntt.co.jp \
    --cc=namei.unix@gmail.com \
    --cc=pbonzini@redhat.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).