This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Synchronisation between a Linux dom0 and a hvm Windows g

To: Quentin Garnier <qgarnier@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Synchronisation between a Linux dom0 and a hvm Windows guest
From: "Mike D. Day" <ncmike@xxxxxxxxxx>
Date: Wed, 26 Jul 2006 09:39:19 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 26 Jul 2006 06:39:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060725141030.1509aedb@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060725141030.1509aedb@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Macintosh/20060530)
Quentin Garnier wrote:

So right now I'm looking for idea to synchronise the two domains that
wouldn't cost me too much in terms of latency.  Getting rid of the
caching issue that seems to be part of the problem would be a start, but
I really lack ideas and I don't really know where to hack to do that in
Linux.  A better way would of course to use Xen to have the relevant
pages explicitely set dirty before reading them in Linux, and something
mostly equivalent in Windows.

Anyone can point to something to start with?

Have you tried simply using IP? Networking is pretty fast between domain 0 and other domains on the same hardware. If you use a pair of tcp sockets synchronization is handled for you.

Of course I'm assuming that you are exchanging data by passing messages via the shared memory. Not sure if that is your actual application. Also, you don't mention your latency and performance requirements.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>