[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 9:21 PM, Jan Beulich <JBeulich@xxxxxxxx> wrote:

As said - I'd want you to evaluate a model without such a new node,
and with instead the requirement placed on the balloon driver to
balloon out pages evenly allocated across the guest's virtual nodes. 
Oh, so you need the experiments' result without this patch?
I see. I'll do it and send the result.

> You are exactly right again, this design is only for Linux balloon driver.
> For Linux, balloon can choose which page to balloon in/out. So we can
> assocate the pages with v-nodeid.
> For the other kinds of architechure, please forgive me that I haven't think
> of that far...

The abstract model shouldn't take OS implementation details or
policies into account; the implementation later of course can (and
frequently will need to).

So, you mean that the abstract model should consider that OS could not
allocate pages by virtual node IDs?
That's a question.. Let me think about it :-)

Yechen Li

Team of System Virtualization and Cloud Computing 
School of Electronic Engineering  and Computer Science

Peking University, China

Nothing is impossible because impossible itself  says: " I'm possible "
lccycc From PKU
Xen-devel mailing list



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