[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 1/2] cpu steal time accounting

  • To: "Rik van Riel" <riel@xxxxxxxxxx>
  • From: "Diwaker Gupta" <diwaker.lists@xxxxxxxxx>
  • Date: Tue, 21 Feb 2006 13:24:13 -0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 21 Feb 2006 21:37:30 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=H2nj9TLxnOPLdxf50jGpp14HmgywrdslnUju5BaEtAzXKHg2uN2TNVPqMKjXWq6jbojGc42TNr5ryMWNgqiphZzhOMAvbmU+XFTkhSpOcjDU2ZuJuaqBZ5qg4PqrKaamTCpYYuXaYQIW/BdYOfU33iG4UD2LBPP1QoRDp9uYI50=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> Basically steal time is the amount of time when:
> 1) we had a runnable task, but
> 2) it was not running, because our vcpu was scheduled
>    away by the hypervisor

Just FYI: XenMon provides a similar metric which we call Waiting Time
-- the time a domain was runnable but not running. Of course, yours is
a different use case, since you want to query the stolen time from
within the guest.

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

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.