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

RE: [Xen-devel] [PATCH][RESUBMIT] don't schedule unplugged vcpus


  • To: "Ryan Harper" <ryanh@xxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Wed, 8 Jun 2005 22:59:43 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 08 Jun 2005 21:59:04 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVsdG4Yerhyei5XTv29PkMn/P0pmQAAF1sA
  • Thread-topic: [Xen-devel] [PATCH][RESUBMIT] don't schedule unplugged vcpus

> > I don't see why we care about vcpus that are down. From the user's 
> > point of view they've gone for good -- it just happens that 
> Xen hasn't 
> > freed the memory in anticipation of it being used again. 
> What do you think?
> 
> I don't think the users care so much as I want tools to be 
> able to extract the current state of affairs for load 
> balancing or other operations that want to account for domain state.

I think the vcpu_to_cpu map contains that. 
The n_vcpu variable isn't really needed: my inclination would be to just
report the number that are currently up, though I'm not hugely fussed.

Best,
Ian

_______________________________________________
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®.