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

Re: [Xen-devel] Credit Scheduler not working correct (3.0.4-0)

  • To: Daniele Palumbo <daniele.palumbo@xxxxxxxxxxxxxxxxx>
  • From: Emmanuel Ackaouy <ackaouy@xxxxxxxxx>
  • Date: Tue, 6 Feb 2007 14:17:58 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 07 Feb 2007 01:19:49 -0800
  • 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=VgkQZea2eIhGed8Set8ohb173lk5Oij1OEjfN56T12ImySjb2xecBy/C4kwe8LLxHxImxnzn62zdy1d4lHmc17BmN94h9seYxScPzs55g/r8YxJk3vYv7EnRoOZaJFZTBZV3qQ88L0nDx4RNX8lcUKY8b15AUch5me6q9AfSnns=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Feb 1, 2007, at 11:58, Daniele Palumbo wrote:
On Thursday 01 February 2007 11:30, Emmanuel Ackaouy wrote:
Also, setting cap=100 on a UP guest is pointless. Just leave it
as zero. A VCPU isn't going to get more than 100% of a physical
CPU anyway.

is pointless if you have only 1 vcpu, right?

Yes, because 100 means 1 physical CPU.
100 * number of VCPUs is the upper bound anyway.

Xen-devel mailing list



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