qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Qemu-block] ping Re: [PATCH v4 00/11] backup-top filte


From: Vladimir Sementsov-Ogievskiy
Subject: Re: [Qemu-devel] [Qemu-block] ping Re: [PATCH v4 00/11] backup-top filter driver for backup
Date: Wed, 7 Nov 2018 10:16:18 +0000

07.11.2018 01:35, John Snow wrote:
>
> On 11/06/2018 12:21 PM, Kevin Wolf wrote:
>> Am 02.11.2018 um 17:41 hat Vladimir Sementsov-Ogievskiy geschrieben:
>>> ping
>>>
>>> 15.10.2018 19:06, Vladimir Sementsov-Ogievskiy wrote:
>>>> Hi all!
>>>>
>>>> These series introduce backup-top driver. It's a filter-node, which
>>>> do copy-before-write operation. Mirror uses filter-node for handling
>>>> guest writes, let's move to filter-node (from write-notifiers) for
>>>> backup too (patch 16)
>>>>
>>>> v4:
>>>> fixes, rewrite driver to be implicit, drop new interfaces and
>>>> don't move to BdrvDirtyBitmap for now, as it's not obvious will
>>>> it be really needed and don't relate to these series more.
>>>>
>>>> v3 was "[PATCH v3 00/18] fleecing-hook driver for backup"
>>>>
>>>> v2 was "[RFC v2] new, node-graph-based fleecing and backup"
>>>>
>>>> These series are based on
>>>>    [PATCH v4 0/8] dirty-bitmap: rewrite bdrv_dirty_iter_next_area
>>>> and
>>>>    [PATCH 0/2] replication: drop extra sync
>> Before we can move forward here, we need to deal with the dependencies.
>> I merged the second one now (because there wasn't any feedback from the
>> replication maintainers), but the first one looks like it was going
>> through John's or Eric's tree?
>>
> I was expecting it to go through Eric's because it was predicated on NBD
> patches that he was staging.
>
> Is that no longer true?

yes, it's merged to master.

> --js


-- 
Best regards,
Vladimir


reply via email to

[Prev in Thread] Current Thread [Next in Thread]