On 12/02/2015 04:07, Wen Congyang wrote:
> Wen Congyang (14):
>   docs: block replication's description
>   quorom: add a new read pattern
>   quorum: ignore 0-length child
>   Add new block driver interfaces to control disk replication
>   quorom: implement block driver interfaces for block replication
>   NBD client: connect to nbd server later
>   NBD client: implement block driver interfaces for block replication
>   block: add a new API to create a hidden BlockBackend
>   block: give backing image its own BlockBackend
>   allow the backing image access the origin BlockDriverState
>   allow writing to the backing file
>   Add disk buffer for block replication
>   COW: move cow interfaces to a seperate file
>   COLO: implement a new block driver

Hi Wen, sorry for the delay.

Kevin and Max need to review this series, as they are the most
comfortable with BlockDriverState vs. BlockBackend.

I suspect you cannot unconditionally give a separate BlockBackend to
each backing image, but they can hopefully suggest how to proceed.

Paolo

Reply via email to