[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160509131158.d5429d4dba4a24c5b1aac9ca@linux-foundation.org>
Date: Mon, 9 May 2016 13:11:58 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Reza Arbab <arbab@...ux.vnet.ibm.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Daniel Kiper <daniel.kiper@...cle.com>,
Dan Williams <dan.j.williams@...el.com>,
Vlastimil Babka <vbabka@...e.cz>,
Tang Chen <tangchen@...fujitsu.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
David Vrabel <david.vrabel@...rix.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
David Rientjes <rientjes@...gle.com>,
Andrew Banman <abanman@....com>,
Chen Yucong <slaoub@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Yasunori Goto <y-goto@...fujitsu.com>,
Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>,
Zhang Zhen <zhenzhang.zhang@...wei.com>,
Shaohua Li <shaohua.li@...el.com>
Subject: Re: [PATCH 0/3] memory-hotplug: improve rezoning capability
On Mon, 9 May 2016 12:53:36 -0500 Reza Arbab <arbab@...ux.vnet.ibm.com> wrote:
> While it is currently possible to rezone memory when it is onlined, there are
> implicit assumptions about the zones:
>
> * To "online_kernel" a block into ZONE_NORMAL, it must currently
> be in ZONE_MOVABLE.
>
> * To "online_movable" a block into ZONE_MOVABLE, it must currently
> be in (ZONE_MOVABLE - 1).
>
> So on powerpc, where new memory is hotplugged into ZONE_DMA, these operations
> do not work.
>
> This patchset replaces the qualifications above with a more general
> validation of zone movement.
>
The patches look good from a first scan. It's late for 4.6 so I'll
queue them for 4.7-rc1, unless there are convincing reasons otherwise?
Hopefully the other memory-hotplug developers will be able to find time
to review these.
Powered by blists - more mailing lists