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

[Dario Faggioli <dario.faggioli@citrix.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1359 bytes --]

On mar, 2014-03-11 at 18:16 +0000, Ian Jackson wrote:
> Dario Faggioli writes ("Re: [Xen-devel] [PATCH 2/4] libxc: report how much memory a domain has on each NUMA node"):
> > 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
> allocations.
> 
Mmm... I think I see what you mean now (except perhaps for the "domain
self-directed numa migration" part).

I also still don't think that this specific call/functionality should be
subject to (that much) locking, at least not at this level, but I see
the value of having a plan.

That, however, is a way bigger thing than what we're discussing here.
I'll start a discussion in another thread.

Thanks and Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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