From: Kevin Wolf <kwolf@redhat.com>
To: Charlie Shepherd <charlie@ctshepherd.com>
Cc: pbonzini@redhat.com, gabriel@kerneis.info, qemu-devel@nongnu.org,
stefanha@gmail.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] COW: Speed up writes
Date: Mon, 11 Nov 2013 17:39:26 +0100 [thread overview]
Message-ID: <20131111163926.GB24359@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1383753568-15844-1-git-send-email-charlie@ctshepherd.com>
Am 06.11.2013 um 16:59 hat Charlie Shepherd geschrieben:
> v3:
> - Refix cow_update_bitmap and squash patches 1 & 3 together to ensuring that we only flush if
> necessary, patch 1 on its own would change this causing a regression.
> v2:
> - Fix bit position calculations in cow_update_bitmap
> - Add necessary check in cow_set_bits
>
> Following on from Paolo's commits 26ae980 and 276cbc7, this patchset
> implements some changes he recommended earlier which I didn't previously have
> time to do while on GSoC.
>
> Charlie Shepherd (2):
> COW: Speed up writes
> COW: Extend checking allocated bits to beyond one sector
>
> block/cow.c | 123 ++++++++++++++++++++++++++++++++++++------------------------
> 1 file changed, 75 insertions(+), 48 deletions(-)
Thanks, applied to the block-next branch for 1.8.
Your lines in the commit message were a bit too long, please try to have
a line break after ~72 characters in future patches (I fixed it up
manually for this one).
Kevin
prev parent reply other threads:[~2013-11-11 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 15:59 [Qemu-devel] [PATCH v3 0/2] COW: Speed up writes Charlie Shepherd
2013-11-06 15:59 ` [Qemu-devel] [PATCH v3 1/2] " Charlie Shepherd
2013-11-06 16:17 ` Paolo Bonzini
2013-11-06 16:24 ` Charlie Shepherd
2013-11-13 12:59 ` Kevin Wolf
2013-11-15 18:43 ` Charlie Shepherd
2013-11-06 15:59 ` [Qemu-devel] [PATCH v3 2/2] COW: Extend checking allocated bits to beyond one sector Charlie Shepherd
2013-11-11 16:39 ` Kevin Wolf [this message]
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=20131111163926.GB24359@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=charlie@ctshepherd.com \
--cc=gabriel@kerneis.info \
--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).