WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Buffered IO for IO?

To: "Zulauf, John" <john.zulauf@xxxxxxxxx>, Mats Petersson <mats@xxxxxxxxxxxxxxxxx>, Trolle Selander <trolle.selander@xxxxxxxxx>
Subject: Re: [Xen-devel] Buffered IO for IO?
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Tue, 24 Jul 2007 07:31:52 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 23 Jul 2007 23:26:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <BD262A443AD428499D90AF8368C4528D8A18BE@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfNW9TTvtFUNzDLShW+WjTgEp4wWAABFb7gABcJmp4=
Thread-topic: [Xen-devel] Buffered IO for IO?
User-agent: Microsoft-Entourage/11.3.3.061214
On 23/7/07 20:38, "Zulauf, John" <john.zulauf@xxxxxxxxx> wrote:

> I'm running on an 8-core system with currently only two HVM domains
> (with currently single VCPU each). Both top on Dom0 and xm top, don't
> seem to indicate qemu-dm as the performance bottleneck.  However, I'm
> not sure about roundtrip latency through the xenstore to qemu and back.

Well, maybe you are just seeing VMEXIT time then. You might try adding some
RDTSC from when a notification is sent to qemu until when your HVM vcpu is
rewoken, and see what the latency looks like. It shouldn't be all that bad
if dom0 is on another cpu and is otherwise fairly idle.

Also, you could see how many characters are sent and received to start a
windbg session. If there are a surprisingly large number of bytes received
then it may be the receive direction is causing more trouble than the
transmit direction.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel