|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: [PATCH 3/3] mm: Extend memory hotplug API to allow memor
To: |
Dave Hansen <dave@xxxxxxxxxxxxxxxxxx> |
Subject: |
[Xen-devel] Re: [PATCH 3/3] mm: Extend memory hotplug API to allow memory hotplug in virtual machines |
From: |
Daniel Kiper <dkiper@xxxxxxxxxxxx> |
Date: |
Tue, 29 Mar 2011 20:32:42 +0200 |
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: |
Tue, 29 Mar 2011 11:48:36 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<1301329524.31700.8440.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: |
<20110328092507.GD13826@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1301329524.31700.8440.camel@nimitz> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.3.28i |
On Mon, Mar 28, 2011 at 09:25:24AM -0700, Dave Hansen wrote:
> On Mon, 2011-03-28 at 11:25 +0200, Daniel Kiper wrote:
> > This patch contains online_page_chain and apropriate functions
> > for registering/unregistering online page notifiers. It allows
> > to do some machine specific tasks during online page stage which
> > is required to implement memory hotplug in virtual machines.
> > Additionally, __online_page_increment_counters() and
> > __online_page_free() function was add to ease generic
> > hotplug operation.
>
> I really like that you added some symbolic constants there. It makes it
> potentially a lot more readable.
>
> My worry is that the next person who comes along is going to _really_
> scratch their head asking why they would use:
> OP_DO_NOT_INCREMENT_TOTAL_COUNTERS or: OP_INCREMENT_TOTAL_COUNTERS.
> There aren't any code comments about it, and the patch description
> doesn't really help.
>
> In the end, we're only talking about a couple of lines of code for each
> case (reordering the function a bit too):
>
> void online_page(struct page *page)
> {
> // 1. pfn-based bits upping the max physical address markers:
> unsigned long pfn = page_to_pfn(page);
> if (pfn >= num_physpages)
> num_physpages = pfn + 1;
> #ifdef CONFIG_FLATMEM
> max_mapnr = max(page_to_pfn(page), max_mapnr);
> #endif
>
> // 2. number of pages counters:
> totalram_pages++;
> #ifdef CONFIG_HIGHMEM
> if (PageHighMem(page))
> totalhigh_pages++;
> #endif
>
> // 3. preparing 'struct page' and freeing:
> ClearPageReserved(page);
> init_page_count(page);
> __free_page(page);
> }
>
> Your stuff already extracted the free stuff very nicely. I think now we
> just need to separate out the totalram_pages/totalhigh_pages bits from
> the num_physpages/max_mapnr ones.
What do you think about __online_page_increment_counters()
(totalram_pages and totalhigh_pages) and
__online_page_set_limits() (num_physpages and max_mapnr) ???
Daniel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|