|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: [PATCH R4 7/7] xen/balloon: Memory hotplug support for X
To: |
Dave Hansen <dave@xxxxxxxxxxxxxxxxxx> |
Subject: |
[Xen-devel] Re: [PATCH R4 7/7] xen/balloon: Memory hotplug support for Xen balloon driver |
From: |
Daniel Kiper <dkiper@xxxxxxxxxxxx> |
Date: |
Thu, 10 Mar 2011 10:02:07 +0100 |
Cc: |
jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, ian.campbell@xxxxxxxxxx, haicheng.li@xxxxxxxxxxxxxxx, konrad.wilk@xxxxxxxxxx, dan.magenheimer@xxxxxxxxxx, v.tolstov@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, rientjes@xxxxxxxxxx, andi.kleen@xxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, fengguang.wu@xxxxxxxxx, Daniel Kiper <dkiper@xxxxxxxxxxxx>, wdauchy@xxxxxxxxx |
Delivery-date: |
Thu, 10 Mar 2011 01:03:47 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<1299628939.9014.3499.camel@nimitz> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<20110308215049.GH27331@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1299628939.9014.3499.camel@nimitz> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.3.28i |
On Tue, Mar 08, 2011 at 04:02:19PM -0800, Dave Hansen wrote:
> On Tue, 2011-03-08 at 22:50 +0100, Daniel Kiper wrote:
> > +static int xen_online_page_notifier(struct notifier_block *nb, unsigned
> > long val, void *v)
> > +{
> > + struct page *page = v;
> > + unsigned long pfn = page_to_pfn(page);
> > +
> > + if (pfn >= num_physpages)
> > + num_physpages = pfn + 1;
> > +
> > + inc_totalhigh_pages();
> > +
> > +#ifdef CONFIG_FLATMEM
> > + max_mapnr = max(pfn, max_mapnr);
> > +#endif
>
> I really don't like that this is a direct copy of online_page() up to
> this point. They're already subtly different. I'm also curious if this
> breaks on 32-bit kernels because of the unconditional
> inc_totalhigh_pages().
>
> If it's done this way, I'd almost guarantee that the first time someone
> fixes a bug or adds a generic feature in online_page() that Xen gets
> missed.
OK, I rewrite this part of code.
> > + 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.
> However, if you're going to use these notifier chains, then we probably
> should use them to full effect. Have a notifier list like this:
>
> 1. generic online_page()
> 2. xen_online_page_notifier() (returns NOTIFY_STOP)
> 3. free_online_page()
>
> Where finish_online_page() does something like this:
>
> finish_online_page(...)
> {
> ClearPageReserved(page);
> init_page_count(page);
> __free_page(page);
> }
OK.
Daniel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|