Re: [Xen-devel] [PATCH 00/19] Virtual NUMA for PV and HVM

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Fri, Nov 21, 2014 at 04:25:34PM +0000, Jan Beulich wrote:
> >>> On 21.11.14 at 16:06, <wei.liu2@xxxxxxxxxx> wrote:
> > memory = 6000
> > vnuma_memory = [3000, 3000]
> 
> So what would
> 
> memory = 6000
> vnuma_memory = [3000, 2000]
> 
> or
> 
> memory = 6000
> vnuma_memory = [3000, 4000]
> 

Those are not valid configurations at the moment. I have checks in libxl
to mandate sum of vnuma_memory equals to memory (in fact, maxmem).

> mean? Redundant specification of values is always a problem...
> Would be possible to extend "memory" to allow for a vector as well
> as a single value?
> 

Yes, I think it can be done in backward compatible way.

> > vnuma_vcpu_map = [0, 1]
> > vnuma_pnode_map = [0, 0]
> > vnuma_vdistances = [10, 30] # optional
> 
> Being optional, would the real distances be used instead? And what

Default value of [10, 20] will be used.

> meaning does this apparently one dimensional array here have for
> the actually two dimensional SLIT? (Read: An example with more
> than two nodes would be useful.)
> 

The first element of [X, Y] is local distance, the second element is
remote distance.

For a 4 node system:

     0    1    2    3
0    X    Y    Y    Y 
1    Y    X    Y    Y
2    Y    Y    X    Y
3    Y    Y    Y    X

Wei.

> Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel