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

Re: [Xen-devel] [RFC v2][PATCH 1/3] docs: design and intended usage for NUMA-aware ballooning

On Fri, Aug 16, 2013 at 10:09 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>> On 16.08.13 at 06:13, Yechen Li <lccycc123@xxxxxxxxx> wrote:
>> +So, in NUMA aware ballooning, ballooning down and up works as follows:
>> +
>> +* target < current usage -- first of all, the ballooning driver uses the
>> +  PNODE\_TO\_VNODE() service (provided by the virtual topology 
>> implementation,
>> +  as explained above) to translate _pnid_ (that it reads from xenstore) to
>> +  the id(s) of the corresponding set of vnode IDs, say _{vnids}_ (which will
> This looks conceptually wrong: The balloon driver should have no
> need to know about pNID-s; it should be the tool stack doing the
> translation prior to writing the xenstore node.

I agree with this -- I would like to point out that to make this work
for ballooning *up*, however, there will need to be a way for the
guest to specify, "please allocate from vnode X", and have Xen
translate the vnode into the appropriate pnode(s).


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.