All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Nan <wangnan0@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wang Nan <wangnan0@huawei.com>, Ingo Molnar <mingo@redhat.com>,
	Yinghai Lu <yinghai@kernel.org>, Mel Gorman <mgorman@suse.de>,
	Dave Hansen <dave.hansen@intel.com>,
	Zhang Yanfei <zhangyanfei@cn.fujitsu.com>,
	peifeiyue@huawei.com, linux-mm@kvack.org, x86@kernel.org,
	linux-ia64@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chris Metcalf <cmetcalf@tilera.com>
Subject: Re: [PATCH v2 7/7] memory-hotplug: tile: suitable memory should go to ZONE_MOVABLE
Date: Tue, 22 Jul 2014 03:09:34 +0000	[thread overview]
Message-ID: <53CDD5EE.1030805@huawei.com> (raw)
In-Reply-To: <1405914402-66212-8-git-send-email-wangnan0@huawei.com>

Hi Andrew,

Please drop patch 7/7 from -mm tree and keep other 6 patches.

arch_add_memory() in tile is different from others: no nid parameter.
Patch 7/7 will block compiling.

I cc this mail to Chris Metcalf and hope he can look at this issue.

Other 6 patches looks good.

On 2014/7/21 11:46, Wang Nan wrote:
> This patch introduces zone_for_memory() to arch_add_memory() on tile to
> ensure new, higher memory added into ZONE_MOVABLE if movable zone has
> already setup.
> 
> This patch also fix a problem: on tile, new memory should be added into
> ZONE_HIGHMEM by default, not MAX_NR_ZONES-1, which is ZONE_MOVABLE.
> 
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
> Cc: Dave Hansen <dave.hansen@intel.com>
> ---
>  arch/tile/mm/init.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/tile/mm/init.c b/arch/tile/mm/init.c
> index bfb3127..22ac6c1 100644
> --- a/arch/tile/mm/init.c
> +++ b/arch/tile/mm/init.c
> @@ -872,7 +872,8 @@ void __init mem_init(void)
>  int arch_add_memory(u64 start, u64 size)
>  {
>  	struct pglist_data *pgdata = &contig_page_data;
> -	struct zone *zone = pgdata->node_zones + MAX_NR_ZONES-1;
> +	struct zone *zone = pgdata->node_zones +
> +		zone_for_memory(nid, start, size, ZONE_HIGHMEM);
>  	unsigned long start_pfn = start >> PAGE_SHIFT;
>  	unsigned long nr_pages = size >> PAGE_SHIFT;
>  
> 



WARNING: multiple messages have this Message-ID (diff)
From: Wang Nan <wangnan0@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wang Nan <wangnan0@huawei.com>,
	linux-ia64@vger.kernel.org, peifeiyue@huawei.com,
	linux-mm@kvack.org, linux-sh@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, Chris Metcalf <cmetcalf@tilera.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Zhang Yanfei <zhangyanfei@cn.fujitsu.com>,
	Mel Gorman <mgorman@suse.de>, Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH v2 7/7] memory-hotplug: tile: suitable memory should go to ZONE_MOVABLE
Date: Tue, 22 Jul 2014 11:09:34 +0800	[thread overview]
Message-ID: <53CDD5EE.1030805@huawei.com> (raw)
In-Reply-To: <1405914402-66212-8-git-send-email-wangnan0@huawei.com>

Hi Andrew,

Please drop patch 7/7 from -mm tree and keep other 6 patches.

arch_add_memory() in tile is different from others: no nid parameter.
Patch 7/7 will block compiling.

I cc this mail to Chris Metcalf and hope he can look at this issue.

Other 6 patches looks good.

On 2014/7/21 11:46, Wang Nan wrote:
> This patch introduces zone_for_memory() to arch_add_memory() on tile to
> ensure new, higher memory added into ZONE_MOVABLE if movable zone has
> already setup.
> 
> This patch also fix a problem: on tile, new memory should be added into
> ZONE_HIGHMEM by default, not MAX_NR_ZONES-1, which is ZONE_MOVABLE.
> 
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
> Cc: Dave Hansen <dave.hansen@intel.com>
> ---
>  arch/tile/mm/init.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/tile/mm/init.c b/arch/tile/mm/init.c
> index bfb3127..22ac6c1 100644
> --- a/arch/tile/mm/init.c
> +++ b/arch/tile/mm/init.c
> @@ -872,7 +872,8 @@ void __init mem_init(void)
>  int arch_add_memory(u64 start, u64 size)
>  {
>  	struct pglist_data *pgdata = &contig_page_data;
> -	struct zone *zone = pgdata->node_zones + MAX_NR_ZONES-1;
> +	struct zone *zone = pgdata->node_zones +
> +		zone_for_memory(nid, start, size, ZONE_HIGHMEM);
>  	unsigned long start_pfn = start >> PAGE_SHIFT;
>  	unsigned long nr_pages = size >> PAGE_SHIFT;
>  
> 

WARNING: multiple messages have this Message-ID (diff)
From: Wang Nan <wangnan0@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wang Nan <wangnan0@huawei.com>, Ingo Molnar <mingo@redhat.com>,
	Yinghai Lu <yinghai@kernel.org>, Mel Gorman <mgorman@suse.de>,
	Dave Hansen <dave.hansen@intel.com>,
	Zhang Yanfei <zhangyanfei@cn.fujitsu.com>,
	peifeiyue@huawei.com, linux-mm@kvack.org, x86@kernel.org,
	linux-ia64@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chris Metcalf <cmetcalf@tilera.com>
Subject: Re: [PATCH v2 7/7] memory-hotplug: tile: suitable memory should go to ZONE_MOVABLE
Date: Tue, 22 Jul 2014 11:09:34 +0800	[thread overview]
Message-ID: <53CDD5EE.1030805@huawei.com> (raw)
In-Reply-To: <1405914402-66212-8-git-send-email-wangnan0@huawei.com>

Hi Andrew,

Please drop patch 7/7 from -mm tree and keep other 6 patches.

arch_add_memory() in tile is different from others: no nid parameter.
Patch 7/7 will block compiling.

I cc this mail to Chris Metcalf and hope he can look at this issue.

Other 6 patches looks good.

On 2014/7/21 11:46, Wang Nan wrote:
> This patch introduces zone_for_memory() to arch_add_memory() on tile to
> ensure new, higher memory added into ZONE_MOVABLE if movable zone has
> already setup.
> 
> This patch also fix a problem: on tile, new memory should be added into
> ZONE_HIGHMEM by default, not MAX_NR_ZONES-1, which is ZONE_MOVABLE.
> 
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
> Cc: Dave Hansen <dave.hansen@intel.com>
> ---
>  arch/tile/mm/init.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/tile/mm/init.c b/arch/tile/mm/init.c
> index bfb3127..22ac6c1 100644
> --- a/arch/tile/mm/init.c
> +++ b/arch/tile/mm/init.c
> @@ -872,7 +872,8 @@ void __init mem_init(void)
>  int arch_add_memory(u64 start, u64 size)
>  {
>  	struct pglist_data *pgdata = &contig_page_data;
> -	struct zone *zone = pgdata->node_zones + MAX_NR_ZONES-1;
> +	struct zone *zone = pgdata->node_zones +
> +		zone_for_memory(nid, start, size, ZONE_HIGHMEM);
>  	unsigned long start_pfn = start >> PAGE_SHIFT;
>  	unsigned long nr_pages = size >> PAGE_SHIFT;
>  
> 


--
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: Wang Nan <wangnan0@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wang Nan <wangnan0@huawei.com>, Ingo Molnar <mingo@redhat.com>,
	Yinghai Lu <yinghai@kernel.org>, Mel Gorman <mgorman@suse.de>,
	Dave Hansen <dave.hansen@intel.com>,
	Zhang Yanfei <zhangyanfei@cn.fujitsu.com>, <peifeiyue@huawei.com>,
	<linux-mm@kvack.org>, <x86@kernel.org>,
	<linux-ia64@vger.kernel.org>, <linuxppc-dev@lists.ozlabs.org>,
	<linux-sh@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Chris Metcalf <cmetcalf@tilera.com>
Subject: Re: [PATCH v2 7/7] memory-hotplug: tile: suitable memory should go to ZONE_MOVABLE
Date: Tue, 22 Jul 2014 11:09:34 +0800	[thread overview]
Message-ID: <53CDD5EE.1030805@huawei.com> (raw)
In-Reply-To: <1405914402-66212-8-git-send-email-wangnan0@huawei.com>

Hi Andrew,

Please drop patch 7/7 from -mm tree and keep other 6 patches.

arch_add_memory() in tile is different from others: no nid parameter.
Patch 7/7 will block compiling.

I cc this mail to Chris Metcalf and hope he can look at this issue.

Other 6 patches looks good.

On 2014/7/21 11:46, Wang Nan wrote:
> This patch introduces zone_for_memory() to arch_add_memory() on tile to
> ensure new, higher memory added into ZONE_MOVABLE if movable zone has
> already setup.
> 
> This patch also fix a problem: on tile, new memory should be added into
> ZONE_HIGHMEM by default, not MAX_NR_ZONES-1, which is ZONE_MOVABLE.
> 
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Cc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
> Cc: Dave Hansen <dave.hansen@intel.com>
> ---
>  arch/tile/mm/init.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/tile/mm/init.c b/arch/tile/mm/init.c
> index bfb3127..22ac6c1 100644
> --- a/arch/tile/mm/init.c
> +++ b/arch/tile/mm/init.c
> @@ -872,7 +872,8 @@ void __init mem_init(void)
>  int arch_add_memory(u64 start, u64 size)
>  {
>  	struct pglist_data *pgdata = &contig_page_data;
> -	struct zone *zone = pgdata->node_zones + MAX_NR_ZONES-1;
> +	struct zone *zone = pgdata->node_zones +
> +		zone_for_memory(nid, start, size, ZONE_HIGHMEM);
>  	unsigned long start_pfn = start >> PAGE_SHIFT;
>  	unsigned long nr_pages = size >> PAGE_SHIFT;
>  
> 



  reply	other threads:[~2014-07-22  3:09 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21  3:46 [PATCH v2 0/7] memory-hotplug: suitable memory should go to ZONE_MOVABLE Wang Nan
2014-07-21  3:46 ` Wang Nan
2014-07-21  3:46 ` Wang Nan
2014-07-21  3:46 ` Wang Nan
2014-07-21  3:46 ` [PATCH v2 1/7] memory-hotplug: add zone_for_memory() for selecting zone for new memory Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21 17:19   ` Sergei Shtylyov
2014-07-21 17:19     ` Sergei Shtylyov
2014-07-21 17:19     ` Sergei Shtylyov
2014-07-21 17:19     ` Sergei Shtylyov
2014-07-21  3:46 ` [PATCH v2 2/7] memory-hotplug: x86_64: suitable memory should go to ZONE_MOVABLE Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46 ` [PATCH v2 3/7] memory-hotplug: x86_32: " Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46 ` [PATCH v2 4/7] memory-hotplug: ia64: " Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46 ` [PATCH v2 5/7] memory-hotplug: ppc: " Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46 ` [PATCH v2 6/7] memory-hotplug: sh: " Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46 ` [PATCH v2 7/7] memory-hotplug: tile: " Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-21  3:46   ` Wang Nan
2014-07-22  3:09   ` Wang Nan [this message]
2014-07-22  3:09     ` Wang Nan
2014-07-22  3:09     ` Wang Nan
2014-07-22  3:09     ` Wang Nan
2014-07-31 20:43     ` Chris Metcalf
2014-07-31 20:43       ` Chris Metcalf
2014-07-31 20:43       ` Chris Metcalf
2014-07-31 20:43       ` Chris Metcalf

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=53CDD5EE.1030805@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=cmetcalf@tilera.com \
    --cc=dave.hansen@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peifeiyue@huawei.com \
    --cc=x86@kernel.org \
    --cc=yinghai@kernel.org \
    --cc=zhangyanfei@cn.fujitsu.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.