On Fri, Nov 21, 2014 at 03:01:58PM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 21, 2014 at 03:06:42PM +, Wei Liu wrote:
> > Hi all
> >
> > This patch series implements virtual NUMA support for both PV and HVM guest.
> > That is, admin can configure via libxl what virtual NUMA topology th
On Fri, Nov 21, 2014 at 03:06:42PM +, Wei Liu wrote:
> Hi all
>
> This patch series implements virtual NUMA support for both PV and HVM guest.
> That is, admin can configure via libxl what virtual NUMA topology the guest
> sees.
>
> This is the stage 1 (basic vNUMA support) and part of stage
>>> On 21.11.14 at 17:55, wrote:
> Nonetheless I'm all for having a configuration option that would meet
> both present and future need. Do you have anything in mind? Are you
> suggesting we should allow specifying every element in SLIT in xl?
I think that would be desirable.
Jan
_
On Fri, Nov 21, 2014 at 04:42:07PM +, Jan Beulich wrote:
> >>> On 21.11.14 at 17:35, wrote:
> > On Fri, Nov 21, 2014 at 04:25:34PM +, Jan Beulich wrote:
> >> >>> On 21.11.14 at 16:06, wrote:
> >> > vnuma_vdistances = [10, 30] # optional
> >>
> >> Being optional, would the real distances
>>> On 21.11.14 at 17:35, wrote:
> On Fri, Nov 21, 2014 at 04:25:34PM +, Jan Beulich wrote:
>> >>> On 21.11.14 at 16:06, wrote:
>> > vnuma_vdistances = [10, 30] # optional
>>
>> Being optional, would the real distances be used instead? And what
>
> Default value of [10, 20] will be used.
T
On Fri, Nov 21, 2014 at 04:25:34PM +, Jan Beulich wrote:
> >>> On 21.11.14 at 16:06, 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 con
>>> On 21.11.14 at 16:06, wrote:
> memory = 6000
> vnuma_memory = [3000, 3000]
So what would
memory = 6000
vnuma_memory = [3000, 2000]
or
memory = 6000
vnuma_memory = [3000, 4000]
mean? Redundant specification of values is always a problem...
Would be possible to extend "memory" to allow for
