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

Re: [Xen-devel] [PATCH 0/6] xen,xend,tools: Add NUMA support to Xen



Le Lundi 31 Juillet 2006 21:09, Ryan Harper a écrit :
> I've respun the NUMA patches against 10874 and I'm re-submitting them
> with the optimizations mentioned [1]previously on the list.  There was a
> request to see the overhead on non-numa/single-node machines.  I've
> re-run those benchmarks (ballooning up from small mem to multi-gig) as
> well as timing the initially domain increase_reservation time to gauge
> the overhead when allocating from the heap.
Hi,

two more points.

For DOM0_PHYSINFO, sockets_per_node is wrong:
      pi->sockets_per_node = 
            num_online_cpus() / cpus_weight(cpu_core_map[0]);
[On ia64, I return the max of sockets per node].

The node_to_cpu field of struct dom0_physinfo is:
    XEN_GUEST_HANDLE(u64) node_to_cpu;
This means the max cpus is 64.
I know cpumap_t is also 64 bits.
I think you'd better to use cpumap_t.

Here we have NUMA machines with 128 cpus.  The question is how to upgrade Xen 
to handle more than 64 cpus.  We can either incease cpumap_t size to 256 
(until we reach a new limit) or use an unlimited cpu structure.

Tristan.

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