Re: [Memory Accounting] was: Re: PVH dom0 creation fails - the system freezes

[Juergen Gross <jgross@suse.com>]

On 26/07/18 13:27, George Dunlap wrote:
> On Thu, Jul 26, 2018 at 12:22 PM, Juergen Gross <jgross@suse.com> wrote:
>> I believe the right way would be to design a proper ballooning interface
>> suitable for all kinds of guests from scratch. This should include how
>> to deal with hotplug of memory or booting with mem < mem_max. Whether
>> PoD should be included should be discussed, too.
> 
> Juergen, what do you think of this interface:  The toolstack looks at
> all the available information about the guest and determines what size
> the guest's balloon needs to be.  It then writes
> memory/target_balloon_size.  The guest balloon driver simply attempts
> to allocate / free memory to make the balloon that size.

This should be per numa node. So memory/node<n>/target-balloon-size
(I don't like the underscores in the node name).

When adding node specific memory hotplug this scheme could be used
for that purpose, too.

So any memory hotplugged will immediately be used by the guest.

That's just stating a fact, no criticism.

> We'll have to leave memory/target handling as is until all old
> versions of the balloon driver disappear.

Sure.

I'd like the guest to write xenstore node
control/feature-per-node-memory to indicate it will use the new
node(s) instead of the memory/target node.


Juergen


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel