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

Re: [Xen-devel] question regarding dom0 scheduling


  • To: "Agarwal, Lomesh" <lomesh.agarwal@xxxxxxxxx>
  • From: Emmanuel Ackaouy <ackaouy@xxxxxxxxx>
  • Date: Fri, 6 Jul 2007 22:26:07 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 06 Jul 2007 13:24:24 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=E5BegU/DpbrLrwr+UzUt9tGZuz8uros/OQVDCe+K+DZ5Yva6pnwha8V1AqUbyzCwjgZzjDhF5IVrG8cT3SKxHPKn7msK38+oZN4OzCAmEnYIryzFhEqtHkEekjVuSV7PlTVEAMoW4IW02VyywE6ycC3HWQ/Tjjd6SFFV/tCxX1U=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Jul 6, 2007, at 22:18, Agarwal, Lomesh wrote:
How does Xen determines dom0 scheduling? Domains get CPU time slices based on weight and cap but how does Xen determine the time slice for dom0? Does dom0 preempt dom0 ever? If I put an infinite loop in dom0, will that halt the system (as domains will never be scheduled)?

dom0 isn't treated any differently than other domains by default.
you can tweak its weight just like any other domain though.


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


 


Rackspace

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