From: Mel Gorman <mgorman@suse.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: qiuxishi <qiuxishi@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Jiang Liu <jiang.liu@huawei.com>,
"qiuxishi@huawei.com" <qiuxishi@huawei.com>,
"bessel.wang@huawei.com" <bessel.wang@huawei.com>,
"wujianguo@huawei.com" <wujianguo@huawei.com>,
"paul.gortmaker@windriver.com" <paul.gortmaker@windriver.com>,
"kamezawa.hiroyu@jp.fujitsu.com" <kamezawa.hiroyu@jp.fujitsu.com>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"rientjes@google.com" <rientjes@google.com>,
Minchan Kim <minchan@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wen Congyang <wency@cn.fujitsu.com>
Subject: Re: [PATCH RESEND] memory hotplug: fix a double register section info bug
Date: Mon, 17 Sep 2012 15:21:30 +0100 [thread overview]
Message-ID: <20120917142130.GH11266@suse.de> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F19D40E81@ORSMSX108.amr.corp.intel.com>
On Fri, Sep 14, 2012 at 04:24:32PM +0000, Luck, Tony wrote:
> > This is an unusual configuration but it's not unheard of. PPC64 in rare
> > (and usually broken) configurations can have one node span another. Tony
> > should know if such a configuration is normally allowed on Itanium or if
> > this should be considered a platform bug. Tony?
>
> We definitely have platforms where the physical memory on node 0
> that we skipped to leave physical address space for PCI mem mapped
> devices gets tagged back at the very top of memory, after other nodes.
>
> E.g. A 2-node system with 8G on each might look like this:
>
> 0-2G RAM on node 0
> 2G-4G PCI map space
> 4G-8G RAM on node 0
> 8G-16GRAM on node 1
> 16G-18G RAM on node 0
>
> Is this the situation that we are talking about? Or something different?
>
This is the type of situation we are talking about. The spanned range of
node 0 includes node 1. The patch needs another revision with a comment
explaining the situation included but otherwise the patch should be
fine.
--
Mel Gorman
SUSE Labs
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: qiuxishi <qiuxishi@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Jiang Liu <jiang.liu@huawei.com>,
"qiuxishi@huawei.com" <qiuxishi@huawei.com>,
"bessel.wang@huawei.com" <bessel.wang@huawei.com>,
"wujianguo@huawei.com" <wujianguo@huawei.com>,
"paul.gortmaker@windriver.com" <paul.gortmaker@windriver.com>,
"kamezawa.hiroyu@jp.fujitsu.com" <kamezawa.hiroyu@jp.fujitsu.com>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"rientjes@google.com" <rientjes@google.com>,
Minchan Kim <minchan@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Wen Congyang <wency@cn.fujitsu.com>
Subject: Re: [PATCH RESEND] memory hotplug: fix a double register section info bug
Date: Mon, 17 Sep 2012 15:21:30 +0100 [thread overview]
Message-ID: <20120917142130.GH11266@suse.de> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F19D40E81@ORSMSX108.amr.corp.intel.com>
On Fri, Sep 14, 2012 at 04:24:32PM +0000, Luck, Tony wrote:
> > This is an unusual configuration but it's not unheard of. PPC64 in rare
> > (and usually broken) configurations can have one node span another. Tony
> > should know if such a configuration is normally allowed on Itanium or if
> > this should be considered a platform bug. Tony?
>
> We definitely have platforms where the physical memory on node 0
> that we skipped to leave physical address space for PCI mem mapped
> devices gets tagged back at the very top of memory, after other nodes.
>
> E.g. A 2-node system with 8G on each might look like this:
>
> 0-2G RAM on node 0
> 2G-4G PCI map space
> 4G-8G RAM on node 0
> 8G-16GRAM on node 1
> 16G-18G RAM on node 0
>
> Is this the situation that we are talking about? Or something different?
>
This is the type of situation we are talking about. The spanned range of
node 0 includes node 1. The patch needs another revision with a comment
explaining the situation included but otherwise the patch should be
fine.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2012-09-17 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 3:43 [PATCH RESEND] memory hotplug: fix a double register section info bug qiuxishi
2012-09-14 3:43 ` qiuxishi
2012-09-14 9:52 ` Mel Gorman
2012-09-14 9:52 ` Mel Gorman
2012-09-14 16:24 ` Luck, Tony
2012-09-14 16:24 ` Luck, Tony
2012-09-17 14:21 ` Mel Gorman [this message]
2012-09-17 14:21 ` Mel Gorman
2012-09-14 11:00 ` Yasuaki Ishimatsu
2012-09-14 11:00 ` Yasuaki Ishimatsu
2012-09-14 20:14 ` Andrew Morton
2012-09-14 20:14 ` Andrew Morton
2012-09-16 10:14 ` xishi qiu
2012-09-18 0:11 ` Yasuaki Ishimatsu
2012-09-18 0:11 ` Yasuaki Ishimatsu
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=20120917142130.GH11266@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bessel.wang@huawei.com \
--cc=jiang.liu@huawei.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=qiuxishi@gmail.com \
--cc=qiuxishi@huawei.com \
--cc=rientjes@google.com \
--cc=tony.luck@intel.com \
--cc=wency@cn.fujitsu.com \
--cc=wujianguo@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.