[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5220616D.6030403@huawei.com>
Date: Fri, 30 Aug 2013 17:10:05 +0800
From: Jianguo Wu <wujianguo@...wei.com>
To: Andrew Morton <akpm@...ux-foundation.org>, <laijs@...fujitsu.com>
CC: <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
<zhangyanfei@...fujitsu.com>, David Rientjes <rientjes@...gle.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Subject: Re: [PATCH 1/5] mm/vmalloc: use N_MEMORY instead of N_HIGH_MEMORY
On 2013/8/30 11:36, Jianguo Wu wrote:
> Since commit 8219fc48a(mm: node_states: introduce N_MEMORY),
> we introduced N_MEMORY, now N_MEMORY stands for the nodes that has any memory,
> and N_HIGH_MEMORY stands for the nodes that has normal or high memory.
>
> The code here need to handle with the nodes which have memory,
> we should use N_MEMORY instead.
>
As Michal pointed out in http://marc.info/?l=linux-kernel&m=137784852720861&w=2,
N_HIGH_MEMORY should be kept in these places, please ignore this series.
Sorry for the noise.
Thanks.
> Signed-off-by: Jianguo Wu <wujianguo@...wei.com>
> ---
> mm/vmalloc.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 13a5495..1152947 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -2573,7 +2573,7 @@ static void show_numa_info(struct seq_file *m, struct vm_struct *v)
> for (nr = 0; nr < v->nr_pages; nr++)
> counters[page_to_nid(v->pages[nr])]++;
>
> - for_each_node_state(nr, N_HIGH_MEMORY)
> + for_each_node_state(nr, N_MEMORY)
> if (counters[nr])
> seq_printf(m, " N%u=%u", nr, counters[nr]);
> }
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists