|
From: | Paolo Bonzini |
Subject: | Re: [PATCH v2 1/7] block-copy: streamline choice of copy_range vs. read/write |
Date: | Fri, 21 May 2021 18:43:52 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 |
On 21/05/21 17:48, Vladimir Sementsov-Ogievskiy wrote:
I keep it thinking about further moving qemu-img convert to block-copy. But I don't even have a plan when to start this work. So, if we want to do something around copy_range here to prepare for thread-safety, let's just drop it for now as unused on top of "[PATCH v2 00/33] block: publish backup-top filter" (you can take one patch that drop copy_range support in backup to your series to not make a dependency). It's not difficult to reimplement it later.
Then we'll have this same conversation later. I would hope that this series goes in before yours.
Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |