From: Wei Yang <richard.weiyang@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Wei Yang <richard.weiyang@gmail.com>,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Mel Gorman <mgorman@suse.de>,
Andrea Arcangeli <aarcange@redhat.com>,
Reza Arbab <arbab@linux.vnet.ibm.com>,
Yasuaki Ishimatsu <yasu.isimatu@gmail.com>,
qiuxishi@huawei.com, Kani Toshimitsu <toshi.kani@hpe.com>,
slaoub@gmail.com, Joonsoo Kim <js1304@gmail.com>,
Andi Kleen <ak@linux.intel.com>,
David Rientjes <rientjes@google.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
Igor Mammedov <imammedo@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes
Date: Thu, 15 Jun 2017 09:03:41 +0800 [thread overview]
Message-ID: <20170615010341.GB16833@WeideMacBook-Pro.local> (raw)
In-Reply-To: <3e0a47c9-d51d-3d73-e876-abc1c5c81080@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On Wed, Jun 14, 2017 at 11:07:31AM +0200, Vlastimil Babka wrote:
>On 06/14/2017 11:06 AM, Wei Yang wrote:
>> On Mon, Jun 12, 2017 at 08:45:02AM +0200, Michal Hocko wrote:
>>> On Mon 12-06-17 12:28:32, Wei Yang wrote:
>>>> On Thu, Jun 08, 2017 at 02:23:18PM +0200, Michal Hocko wrote:
>>>>> From: Michal Hocko <mhocko@suse.com>
>>>>>
>>>>> movable_node kernel parameter allows to make hotplugable NUMA
>>>>> nodes to put all the hotplugable memory into movable zone which
>>>>> allows more or less reliable memory hotremove. At least this
>>>>> is the case for the NUMA nodes present during the boot (see
>>>>> find_zone_movable_pfns_for_nodes).
>>>>>
>>>>
>>>> When movable_node is enabled, we would have overlapped zones, right?
>>>
>>> It won't based on this patch. See movable_pfn_range
>>
>> I did grep in source code, but not find movable_pfn_range.
>
>This patch is adding it.
>
Oops, what a shame.
>> Could you share some light on that?
>>
>>>
--
Wei Yang
Help you, Help me
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-06-15 1:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 12:23 [PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes Michal Hocko
2017-06-10 14:33 ` Wei Yang
2017-06-12 6:35 ` Michal Hocko
2017-06-11 1:45 ` Wei Yang
2017-06-12 6:37 ` Michal Hocko
2017-06-12 4:28 ` Wei Yang
2017-06-12 6:45 ` Michal Hocko
2017-06-14 9:06 ` Wei Yang
2017-06-14 9:07 ` Vlastimil Babka
2017-06-15 1:03 ` Wei Yang [this message]
2017-06-15 3:13 ` Wei Yang
2017-06-15 8:16 ` Michal Hocko
2017-06-12 8:58 ` Vlastimil Babka
2017-06-12 11:12 ` [PATCH -v2] " Michal Hocko
2017-06-15 3:29 ` [PATCH] " Wei Yang
2017-06-15 8:24 ` Michal Hocko
2017-06-15 15:43 ` Reza Arbab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170615010341.GB16833@WeideMacBook-Pro.local \
--to=richard.weiyang@gmail.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arbab@linux.vnet.ibm.com \
--cc=daniel.kiper@oracle.com \
--cc=imammedo@redhat.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=qiuxishi@huawei.com \
--cc=rientjes@google.com \
--cc=slaoub@gmail.com \
--cc=toshi.kani@hpe.com \
--cc=vbabka@suse.cz \
--cc=vkuznets@redhat.com \
--cc=yasu.isimatu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).