From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, mreitz@redhat.com, kwolf@redhat.com,
vsementsov@virtuozzo.com, jsnow@redhat.com, pbonzini@redhat.com,
stefanha@redhat.com, eesposit@redhat.com
Subject: [PATCH 0/2] block-copy: small fix and refactor
Date: Fri, 28 May 2021 17:16:26 +0300 [thread overview]
Message-ID: <20210528141628.44287-1-vsementsov@virtuozzo.com> (raw)
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(-)
--
2.29.2
next reply other threads:[~2021-05-28 14:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 14:16 Vladimir Sementsov-Ogievskiy [this message]
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 ` [PATCH 0/2] block-copy: small fix and refactor Stefan Hajnoczi
2021-06-02 12:21 ` 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=20210528141628.44287-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.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=stefanha@redhat.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).