[Xen-devel] Re: [PATCH R4 7/7] xen/balloon: Memory hotplug support for Xen balloon driver

[Dave Hansen <dave@xxxxxxxxxxxxxxxxxx>]

On Thu, 2011-03-10 at 10:02 +0100, Daniel Kiper wrote:
> On Tue, Mar 08, 2011 at 04:02:19PM -0800, Dave Hansen wrote:
> > > + mutex_lock(&balloon_mutex);
> > > +
> > > + __balloon_append(page);
> > > +
> > > + if (balloon_stats.hotplug_pages)
> > > +         --balloon_stats.hotplug_pages;
> > > + else
> > > +         --balloon_stats.balloon_hotplug;
> > > +
> > > + mutex_unlock(&balloon_mutex);
> > > +
> > > + return NOTIFY_STOP;
> > > +}
> >
> > I'm not a _huge_ fan of these notifier chains, but I guess it works.
> 
> Could you tell me why ??? I think that in that case new
> (faster, simpler, etc.) mechanism is an overkill. I prefer
> to use something which is writen, tested and ready for usage.

Personally, I find it much harder to figure out what's going on there
than if we had some #ifdefs or plain old function calls.  

It would be one thing if we really had a large or undefined set of
things that needs to interact here, but we really just need to
conditionally free the page either in to the buddy allocator or back to
Xen.  I think that calls for a simpler mechanism than notifier_blocks.

-- Dave


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel