From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54701) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cOcrS-0007J1-LW for qemu-devel@nongnu.org; Tue, 03 Jan 2017 23:07:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cOcrR-0000E9-PG for qemu-devel@nongnu.org; Tue, 03 Jan 2017 23:07:38 -0500 Date: Tue, 3 Jan 2017 23:07:28 -0500 From: Jeff Cody Message-ID: <20170104040728.GA30425@localhost.localdomain> References: <20161129113245.32724-1-pbonzini@redhat.com> <3f948687-3169-c304-3ef8-31347f08857f@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3f948687-3169-c304-3ef8-31347f08857f@redhat.com> Subject: Re: [Qemu-devel] [PATCH for-2.9 v3 0/5] Sheepdog cleanups List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, Hitoshi Mitake , Liu Yuan , qemu-block@nongnu.org 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).