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-ia64-devel

RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb

To: "Xu, Anthony" <anthony.xu@xxxxxxxxx>, "Williamson, Alex (Linux Kernel Dev)" <alex.williamson@xxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Mon, 10 Apr 2006 09:20:36 -0700
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 10 Apr 2006 09:20:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZcq7LX/2eAEZLZRf2UEjafNqjGygAARoawAAMdXuA=
Thread-topic: [Xen-ia64-devel] [PATCH] [Resend]Enable hash vtlb
> >> The attachment is the script which I used to get kernel 
> build performance.
> >> Usage Example,
> >> ./make_kernel.sh    2    /root/linux-2.6.16.tar.bz2
> >>                   (times of build)   (absolute path)
> >
> >   The attachment seems to have been lost to a virus 
> scanner.  My test
> >was simply:
> >
> Almost same
> Thanks
> Anthony
> 
> ># make clean
> ># time make > /dev/null 2>&1
> >repeat
> >
> >Thanks,
> >     Alex

I wonder if the time command is appropriate for measuring
performance in a domU?  Are we sure the "real" component
is measuring elapsed wall clock time?  If not, perhaps
"time" is not accounting for time spent in the hypervisor
and time spent in dom0 (e.g. backend drivers).

In all my past measurements, I've used "date +%s" before
and after and subtracted the difference.

Even if "time" checks out OK, I am still astonished if domU
is faster than native and suspect that there is something
wrong with either the measurement or the methodology.

Dan

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

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