linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Xishi Qiu <qiuxishi@huawei.com>
To: Gu Zheng <guz.fnst@cn.fujitsu.com>
Cc: Yasuaki Ishimatsu <yasu.isimatu@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	izumi.taku@jp.fujitsu.com, Tang Chen <tangchen@cn.fujitsu.com>,
	Xiexiuqi <xiexiuqi@huawei.com>, Mel Gorman <mgorman@suse.de>,
	David Rientjes <rientjes@google.com>,
	Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2 V2] memory-hotplug: fix BUG_ON in move_freepages()
Date: Mon, 20 Apr 2015 10:59:37 +0800	[thread overview]
Message-ID: <55346B99.2060602@huawei.com> (raw)
In-Reply-To: <55345FC4.4070404@cn.fujitsu.com>

On 2015/4/20 10:09, Gu Zheng wrote:

> Hi Ishimatsu, Xishi,
> 
> On 04/20/2015 10:11 AM, Yasuaki Ishimatsu wrote:
> 
>>
>>> When hot adding memory and creating new node, the node is offline.
>>> And after calling node_set_online(), the node becomes online.
>>>
>>> Oh, sorry. I misread your ptaches.
>>>
>>
>> Please ignore it...
> 
> Seems also a misread to me.
> I clear it (my worry) here:
> If we set the node size to 0 here, it may hidden more things than we experted.
> All the init chunks around with the size (spanned/present/managed...) will
> be non-sense, and the user/caller will not get a summary of the hot added node
> because of the changes here.
> I am not sure the worry is necessary, please correct me if I missing something.
> 
> Regards,
> Gu
> 

Hi Gu,

My patch is just set size to 0 when hotadd a node(old or new). I know your worry,
but I think it is not necessary.

When we calculate the size, it uses "arch_zone_lowest_possible_pfn[]" and "memblock",
and they are both from boot time. If we hotadd a new node, the calculated size is
0 too. When add momery, __add_zone() will grow the size and start.

Thanks,
Xishi Qiu

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-04-20  3:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 10:50 [PATCH 1/2 V2] memory-hotplug: fix BUG_ON in move_freepages() Xishi Qiu
2015-04-17 20:05 ` Yasuaki Ishimatsu
2015-04-20  1:33   ` Xishi Qiu
2015-04-20  1:56     ` Yasuaki Ishimatsu
2015-04-20  2:11     ` Yasuaki Ishimatsu
2015-04-20  2:08       ` Gu Zheng
2015-04-20  2:09       ` Gu Zheng
2015-04-20  2:59         ` Xishi Qiu [this message]
2015-04-20  3:15           ` Yasuaki Ishimatsu
2015-04-20  3:34             ` Xishi Qiu
2015-04-20  2:23     ` Yasuaki Ishimatsu
2015-04-20  1:42   ` Gu Zheng
2015-04-20  2:45     ` Xishi Qiu
2015-04-20  3:29       ` Yasuaki Ishimatsu
2015-04-20  3:42         ` Xishi Qiu
2015-04-20 18:23           ` Yasuaki Ishimatsu
2015-04-21  1:31             ` Xishi Qiu

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=55346B99.2060602@huawei.com \
    --to=qiuxishi@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=rientjes@google.com \
    --cc=tangchen@cn.fujitsu.com \
    --cc=xiexiuqi@huawei.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).