From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH RFC] remus: implement remus replicated
	checkpointing disk
Date: Wed, 12 Mar 2014 20:28:14 +0800
Message-ID: <532052DE.80908@cn.fujitsu.com>
References: <1392023972-24675-1-git-send-email-laijs@cn.fujitsu.com>		
	<1393383209-4449-1-git-send-email-laijs@cn.fujitsu.com>		
	<CAP8mzPOmmeyQhGTWDG79rZ8e+JJHPoT1BTOB+kqzn0KOd-mbUQ@mail.gmail.com>		
	<531FC7F3.5060202@cn.fujitsu.com>	
	<1394618836.21145.11.camel@kazak.uk.xensource.com>	
	<53204B95.6060901@cn.fujitsu.com>
	<1394626654.21145.45.camel@kazak.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1394626654.21145.45.camel@kazak.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Dong Eddie <eddie.dong@intel.com>, FNST-Wen Congyang <wency@cn.fujitsu.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Andrew Cooper <andrew.cooper3@citrix.com>, Jiang Yunhong <yunhong.jiang@intel.com>, Ian Jackson <ian.jackson@eu.citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, rshriram@cs.ubc.ca, Roger Pau Monne <roger.pau@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 03/12/2014 08:17 PM, Ian Campbell wrote:
> On Wed, 2014-03-12 at 19:57 +0800, Lai Jiangshan wrote:
>> On 03/12/2014 06:07 PM, Ian Campbell wrote:
>>> On Wed, 2014-03-12 at 10:35 +0800, Lai Jiangshan wrote:
>>>>> 2. The tapdisk based replication unfortunately is outdated. Please correct me if I have got this wrong.
>>>>> Haven't we decided to get rid of blktap2 and go with the qemu disk models? In which case, the tapdisk
>>>>> remus code has to be ported into some qemu disk variant.
>>>>
>>>> We are implementing *qemu* replicated checkpointing disk, but we can't make it public even we have done,
>>>> we need to delay the publication due to we are paid to implement it by a paid customer.
>>>
>>> Are you saying you are never going to be able to make this code public?
>>> Or just that it will be delayed by some months?
>>
>> It will be just delayed, but it will be public finally.
>>
>> This private code is just under implementing, it is far from mature.
>> I hope the community also makes efforts to it.
> 
> Are you asking that people work on this feature in parallel with you
> building the same thing privately? That doesn't seem likely.
> 

It may or may not be the same. our private implementing is too slow,
If the community do it so, we will definitely join in.