From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43809) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YlECH-0008MW-6Y for qemu-devel@nongnu.org; Thu, 23 Apr 2015 06:17:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YlECG-00075g-48 for qemu-devel@nongnu.org; Thu, 23 Apr 2015 06:17:29 -0400 Date: Thu, 23 Apr 2015 12:17:16 +0200 From: Kevin Wolf Message-ID: <20150423101716.GF5289@noname.redhat.com> References: <1428055280-12015-1-git-send-email-wency@cn.fujitsu.com> <1428055280-12015-2-git-send-email-wency@cn.fujitsu.com> <20150420153047.GB32653@stefanha-thinkpad.redhat.com> <5535A727.5080402@cn.fujitsu.com> <55366C81.1080202@redhat.com> <20150422093101.GD3882@noname.redhat.com> <5537742A.90504@redhat.com> <20150423090031.GB5289@noname.redhat.com> <5538B813.5090506@cn.fujitsu.com> <5538C3CC.9030902@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5538C3CC.9030902@redhat.com> Subject: Re: [Qemu-devel] [PATCH COLO v3 01/14] docs: block replication's description List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Fam Zheng , Lai Jiangshan , qemu block , Jiang Yunhong , Dong Eddie , qemu devel , Max Reitz , Gonglei , Stefan Hajnoczi , Yang Hongyang , "Dr. David Alan Gilbert" , zhanghailiang Am 23.04.2015 um 12:05 hat Paolo Bonzini geschrieben: > > > On 23/04/2015 11:14, Wen Congyang wrote: > > The bs->file->driver should support backing file, and use backing reference > > already. > > > > What about the primary side? We should control when to connect to NBD server, > > not in nbd_open(). Why do you need to create the block device before the connection should be made? > My naive suggestion could be to add a BDRV_O_NO_CONNECT option to > bdrv_open and a separate bdrv_connect callback. Open would fail if > BDRV_O_NO_CONNECT is specified and drv->bdrv_connect is NULL. > > You would then need a way to have quorum pass BDRV_O_NO_CONNECT. Please don't add new flags. If we have to, we can introduce a new option (in the QDict), but first let's check if it's really necessary. > Perhaps quorum is not a great match after all, and it's better to add a > new "colo" driver similar to quorum but simpler and only using the read > policy that you need for colo. The new driver would also know how to > use BDRV_O_NO_CONNECT. In any case the amount of work needed would not > be too big. I thought the same, but haven't looked at the details yet. But if I understand correctly, the plan is to take quorum and add options to turn off the functionality of using a quorum - that's a bit odd. What I think is really needed here is essentially an active mirror filter. Kevin