On Thu, Oct 18, 2007 at 10:10:59AM +0900, Saori Fukuta wrote:
On Wed, 17 Oct 2007 10:53:17 -0400 Daniel Veillard wrote:
On Thu, Oct 11, 2007 at 10:45:44AM -0500, Ryan Harper wrote:
I think we should support the same cpuset notation that Xen supports,
which means including ranges (1-4) and
On Thu, Oct 18, 2007 at 04:53:15AM -0400, Daniel Veillard wrote:
On Wed, Oct 17, 2007 at 10:14:56PM -0400, beth kon wrote:
This is certainly a nit, but I might change parseCpuNumber to
parseNumber, since it looks a little odd that you are getting the cell
id from the cpu number. A nit to
On Thu, Oct 11, 2007 at 10:45:44AM -0500, Ryan Harper wrote:
* Daniel Veillard [EMAIL PROTECTED] [2007-10-11 08:01]:
- for the mapping at the XML level I suggest to use a simple extension
to the vcpun/vcpu and extend it to
vcpu cpuset='2,3'n/vcpu
with a limited syntax
On Fri, Oct 12, 2007 at 05:02:11PM +0900, Saori Fukuta wrote:
On Thu, 11 Oct 2007 09:00:14 -0400 Daniel Veillard wrote:
- for the mapping at the XML level I suggest to use a simple extension
to the vcpun/vcpu and extend it to
vcpu cpuset='2,3'n/vcpu
with a limited syntax
On Fri, 12 Oct 2007 05:12:13 -0400 Daniel Veillard wrote:
On Fri, Oct 12, 2007 at 05:02:11PM +0900, Saori Fukuta wrote:
On Thu, 11 Oct 2007 09:00:14 -0400 Daniel Veillard wrote:
- for the mapping at the XML level I suggest to use a simple extension
to the vcpun/vcpu and extend it
There are a few things I gathered on this issue. This affects
NUMA setups, where basically if a domain must be placed on a given cell
it is not good to let the hypervisor place it first with its own heuristics
and then later migrate it to a different set of CPU, but better to
instruct the
* Daniel Veillard [EMAIL PROTECTED] [2007-10-11 08:01]:
There are a few things I gathered on this issue. This affects
NUMA setups, where basically if a domain must be placed on a given cell
it is not good to let the hypervisor place it first with its own heuristics
and then later migrate it
