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] credit scheduler error rates as reported by HP and UCSD

To: ncmike@xxxxxxxxxx
Subject: Re: [Xen-devel] credit scheduler error rates as reported by HP and UCSD
From: "Diwaker Gupta" <diwaker.lists@xxxxxxxxx>
Date: Thu, 12 Apr 2007 09:09:14 -0700
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Emmanuel Ackaouy <ackaouy@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, lucy.cherkasova@xxxxxx
Delivery-date: Thu, 12 Apr 2007 09:08:02 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dSS2LE/sFbsjhp1hlKdH8P5pTqSHG2mcbt7I2wjskF86OpVg68+TUjSSbZO3yy/fBoxhLSc+SeuWPeBnniaukdERmjKEqgjSa7ClW+Rb7rJ+KWq8aWLwehKxc8b8iIKgQhgH6hZVPMyGA57jp6hVv/sbWTeOAsp/kOXzFLtddX8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=M3JJEGwkj3W0HA1a6pucnITiX75YCZugXOvDLnQojpIjjeXoPhys3Gv3pbvaeCHpSzgjhoqLERG1dUyYeStnUqXGOlYEYnEaUsA8XQmqmJxdLYIz5kmXCk6R4QEm1+hgATocqnOJNCfGdmJ+E5U2pFiqqLGQ8VLdhnuhL4yKi/k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070412151550.GF14282@xxxxxxxxxxxxxxxxxxxxxx>
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: <20070412151550.GF14282@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Questions: how does ALERT measure actual cpu allocation? Using Xenmon?
How does the ALERT exersize the domain? The paper didn't mention the
actual system calls and hypercalls the domains are making when running
ALERT.

yes, we use XenMon. We also have xentop output for correlation and validation.

I think the paper describes the workloads we use. When the VMs are
running webservers, we use httperf to generate the workload. The iperf
benchmark uses the iperf bandwidth measurement tools and I believe the
VMs run as iperf servers. For disk I/O, we just use a regular dd
command to read a file into /dev/null.

I'm not sure how one would accurately generate the set of system calls
and hypercalls generated by a given workload. And how would you use
this information if you had it?

Diwaker
--
Web/Blog/Gallery: http://floatingsun.net/blog

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

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