Re: CPU pinning of domains at creation time

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

 



On Thu, Oct 11, 2007 at 10:45:44AM -0500, Ryan Harper wrote:
> * Daniel Veillard <veillard@xxxxxxxxxx> [2007-10-11 08:01]:
> >    - for the mapping at the XML level I suggest to use a simple extension
> >      to the <vcpu>n</vcpu> and extend it to
> >      <vcpu cpuset='2,3'>n</vcpu>
> >      with a limited syntax which is just the comma separated list of
> >      allowed CPU numbers (if the code actually detects such a cpuset is
> >      in effect i.e. in general this won't be added).
> 
> I think we should support the same cpuset notation that Xen supports,
> which means including ranges (1-4) and negation (^1).  These two
> features make describing large ranges much more compact.

  on input I guess it makes sense. But we can't garantee to have such
a compact representation on output.

Daniel

-- 
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard      | virtualization library  http://libvirt.org/
veillard@xxxxxxxxxx  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine  http://rpmfind.net/

--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]