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

[Xen-devel] Minimum time-quantum for a DomU

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Amitayu Das" <amitayudas@xxxxxxxxx>
  • Date: Tue, 21 Mar 2006 07:47:28 -0500
  • Delivery-date: Tue, 21 Mar 2006 12:48:41 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=llah0izK6LJsZGhMPLHWt4K4uJ0nYLDizXUjF/aM1TGbc1rZiOvO1xVnoUDdrcW/A93ijbbSYhUHFUGYgjfnR5LZ/06JH8d6Qr2ozROLwrT/LxpNetM+9c8I8390sg15PoPiqL526mS8xTe8pd3bcl0szxb1LFP7wqoKDvMDDeI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


How can we know about the minimum time-quantum that a Xen scheduler
allocates for a DomU? How big or less is that compared to the
of one jiffy? Please note that I'm not asking for a slice value within a period. In order to schedule a DomU for a total time of slice value within a period, what is the minimum time that a DomU would be scheduled by Hypervisor each time within a period? I'm asking w.r.t. default settings available with Xen 3.0 and sedf scheduler.

If anybody knows, please let me know.

Xen-devel mailing list



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