From: Stefan Hajnoczi <stefanha@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: kwolf@redhat.com, eesposit@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, mreitz@redhat.com, pbonzini@redhat.com,
jsnow@redhat.com
Subject: Re: [PATCH 0/2] block-copy: small fix and refactor
Date: Wed, 2 Jun 2021 10:13:18 +0100 [thread overview]
Message-ID: <YLdLrrTszu8MMxPv@stefanha-x1.localdomain> (raw)
In-Reply-To: <20210528141628.44287-1-vsementsov@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
On Fri, May 28, 2021 at 05:16:26PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> This is my suggestion how to refactor block-copy to avoid extra atomic
> operations in
> "[PATCH v2 0/7] block-copy: protect block-copy internal structures"
>
> Vladimir Sementsov-Ogievskiy (2):
> block-copy: fix block_copy_task_entry() progress update
> block-copy: refactor copy_range handling
>
> block/block-copy.c | 79 +++++++++++++++++++++++++++++++---------------
> 1 file changed, 53 insertions(+), 26 deletions(-)
I posted suggestions for the doc comment on Patch 2, otherwise:
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-06-02 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 14:16 [PATCH 0/2] block-copy: small fix and refactor Vladimir Sementsov-Ogievskiy
2021-05-28 14:16 ` [PATCH 1/2] block-copy: fix block_copy_task_entry() progress update Vladimir Sementsov-Ogievskiy
2021-05-28 14:16 ` [PATCH 2/2] block-copy: refactor copy_range handling Vladimir Sementsov-Ogievskiy
2021-06-02 9:12 ` Stefan Hajnoczi
2021-06-02 11:43 ` Vladimir Sementsov-Ogievskiy
2021-06-02 9:13 ` Stefan Hajnoczi [this message]
2021-06-02 12:21 ` [PATCH 0/2] block-copy: small fix and refactor Kevin Wolf
2021-06-03 7:38 ` Paolo Bonzini
2021-06-07 15:10 ` Kevin Wolf
2021-06-07 15:16 ` Emanuele Giuseppe Esposito
2021-06-07 16:18 ` Vladimir Sementsov-Ogievskiy
2021-06-07 19:08 ` Emanuele Giuseppe Esposito
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=YLdLrrTszu8MMxPv@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=eesposit@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).