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

Re: [Xen-devel] [PATCH 2/4] libxc: report how much memory a domain has on each NUMA node

Dario Faggioli writes ("Re: [Xen-devel] [PATCH 2/4] libxc: report how much 
memory a domain has on each NUMA node"):
> On mar, 2014-03-11 at 11:15 +0000, Ian Jackson wrote:
> > We have had problems before with toolstack memory balancing and
> > managemetn algorithms needing information which wasn't properly
> > available.  So I think I want to see an explanation how this would be
> > used in an actual memory balancing/assignment algorith.
> > 
> I'm not sure why you're asking this. For now, this is not going to be
> used in any algorithm, it's pure information reporting.

An API is for life, not just "for now".

> In the current NUMA placement implementation, in libxl, what we need to
> know is how much memory is free on each node, rather than how much
> memory each domain occupies there.
> So, what is it that I should try to show you?

I want a sketch of a race-free memory assignment approach that works
with ballooning (and domain self-directed numa migration), and doesn't
depend on arbitrating memory usage by having Xen fail certain memory


Xen-devel mailing list



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