From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:43070)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <omamluk@zerto.com>) id 1S43mp-0004jL-LQ
	for qemu-devel@nongnu.org; Sun, 04 Mar 2012 00:15:12 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <omamluk@zerto.com>) id 1S43mn-0001tC-Pa
	for qemu-devel@nongnu.org; Sun, 04 Mar 2012 00:15:11 -0500
Received: from mail-ww0-f53.google.com ([74.125.82.53]:41764)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <omamluk@zerto.com>) id 1S43mn-0001sB-J8
	for qemu-devel@nongnu.org; Sun, 04 Mar 2012 00:15:09 -0500
Received: by wgbfm10 with SMTP id fm10so1484438wgb.10
	for <qemu-devel@nongnu.org>; Sat, 03 Mar 2012 21:15:06 -0800 (PST)
Message-ID: <4F52FA48.9050903@zerto.com>
Date: Sun, 04 Mar 2012 07:14:48 +0200
From: Ori Mamluk <omamluk@zerto.com>
MIME-Version: 1.0
References: <73865e0ce364c40e0eb65ec6b22b819d@mail.gmail.com>
	<4F31153E.9010205@codemonkey.ws> <4F311839.9030709@redhat.com>
	<e2d5747f27ca519ddc6b7f0133e0a1a8@mail.gmail.com>
	<4F311BBA.8000708@codemonkey.ws> <4F312FD3.5020206@zerto.com>
	<4F3137DB.1040503@redhat.com> <4F3139CE.4040103@zerto.com>
	<4F314798.8010009@redhat.com> <4F3211D0.3070502@zerto.com>
	<4F323875.1000000@redhat.com> <4F3244C2.1040604@zerto.com>
	<4F32489A.80307@redhat.com> <4F32788C.60904@zerto.com>
	<CAJSP0QXRdU4XhW2wU+vOPh+vuzEECdKEWUGzaaENEtTbpRfKMg@mail.gmail.com>
	<4F40FBD6.2000500@zerto.com> <4F425987.20103@redhat.com>
	<4F435DD2.8080600@redhat.com> <4F4DE40C.9020001@zerto.com>
	<CAJSP0QWOd-q-W3LcV1THYy_XPTk2XPvdLth+v-B+iC22n-4HZA@mail.gmail.com>
In-Reply-To: <CAJSP0QWOd-q-W3LcV1THYy_XPTk2XPvdLth+v-B+iC22n-4HZA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] BlockDriverState stack and BlockListeners
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, =?UTF-8?B?16rXldee16gg15HXnyDXkNeV16g=?= <tomer@zertodata.com>, =?UTF-8?B?16LXldeT15Mg16fXk9ed?= <oded@zerto.com>, dlaor@redhat.com, qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>, Zhi Yong Wu <zwu.kernel@gmail.com>, Federico Simoncelli <fsimonce@redhat.com>, Yair Kuszpet <yairk@zerto.com>, Paolo Bonzini <pbonzini@redhat.com>

On 03/03/2012 13:46, Stefan Hajnoczi wrote:
> On Wed, Feb 29, 2012 at 8:38 AM, Ori Mamluk<omamluk@zerto.com>  wrote:
>> I think the BlockFilter direction goes very well with our plans for a
>> replication module.
>> I guess it would take some discussions and time to form a solid layer for
>> the BlockFilters, and I'd like to move ahead in parallel with the
>> replication module.
> Will the replicatoin module still use a custom network protocol or do
> you plan to implement the in-process NBD server?
>
> I have added the in-process NBD server idea to the Google Summer of
> Code 2012 project ideas page.  Perhaps students will be interested in
> implementing it this summer.  But if you are already working on it I
> can remove the idea, please let me know.
>
> Thanks,
> Stefan
I prefer not to do it as NBD server, mainly because NBD by definition 
requires a port per volume and I think it will pose a management overhead.
So my current plan is a custom protocol - but it's still TBD.