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

Re: [Xen-devel] [PATCH 1/1] xen/balloon: Enforce various limits on target

On Thu, Mar 07, 2013 at 12:07:09PM +0000, David Vrabel wrote:
> On 07/03/13 11:28, Daniel Kiper wrote:
> > On Wed, Mar 06, 2013 at 05:52:28PM +0000, David Vrabel wrote:
> >
> >> If you set the target above d->max_pages you won't be able to populate 
> >> them.
> >>
> >> So, using the maximum_reservation call seems like the right thing to me.
> >
> > Please look above. If you use this value you would not
> > be able to increase reservation.
> I don't think I'm understanding the use case you're talking about.
> Do you mean we should allow a target <= d->tot_pages even if this is
> above d->max_pages?  I agree with this.
> Something like this:
> void balloon_set_new_target(unsigned long target)
> {
>       domid_t domid = DOMID_SELF;
>       int rc;
>       unsigned long host_limit;
>       target = min(target, MAX_DOMAIN_PAGES);
>       /* Prevent target from attempting the expand the reservation
>          above the max enforced by the hypervisor. */
>       rc = HYPERVISOR_memory_op(XENMEM_maximum_reservation, &domid);
>       if (rc > 0) {
>               host_limit = rc;
>               target = min(target,
>                       max(host_limit, balloon_stats.current_pages));
>       }
>       balloon_stats.target_pages = target;
>       schedule_delayed_work(&balloon_worker, 0);
> }

I dug deeper into Xen source and found some strange things for me.

If you call xl mem-set it does two things:
  - sets target in xenstore,
  - sets d->max_pages (sic!).

Last thing is very confusing because at least command comment
does mention nothing about this behavior. Comment for this
command states: "Set the current memory usage for a domain".
It does say nothing about setting memory usage limit. IMO it is
the role of xl mem-max (another strange thing is that xl mem-max
sets d->max_pages but does not touch static-max; I think it should
be changed too; now it is not possible to increase limit above
maxmem defined at startup which makes memory hotplug practically
unusable). That is why xl mem-set behavior should be changed
(IIRC xm sets only target in xenstore) or comment should be aligned
to what xl code doas in real. Then we could back to discussion about
new balloon_set_new_target().


Xen-devel mailing list



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