[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXKxnx5kiuz6zfcfS4pKJJu6GOR6CWso-wKcZuHBaAzbQ@mail.gmail.com>
Date: Sun, 10 Mar 2013 23:29:49 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Tang Chen <tangchen@...fujitsu.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>, Thomas Renninger <trenn@...e.de>,
linux-kernel@...r.kernel.org, Pekka Enberg <penberg@...nel.org>,
Jacob Shin <jacob.shin@....com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: Re: [PATCH v2 20/20] x86, mm, numa: Put pagetable on local node ram
for 64bit
On Sun, Mar 10, 2013 at 10:49 PM, Tang Chen <tangchen@...fujitsu.com> wrote:
> On 03/10/2013 02:44 PM, Yinghai Lu wrote:
>>
>> Calling init_mem_mapping in early_initmem_init for every node.
>> alloc_low_pages will alloc page table in following order:
>> BRK, local node, low range
>> So page table will be on low range or local nodes.
...
> IIUC, we call init_mem_mapping() for each node ranges. In the first time,
> local_max_pfn_mapped = begin >> PAGE_SHIFT;
> local_min_pfn_mapped = real_end >> PAGE_SHIFT;
> which means
> local_min_pfn_mapped >= local_max_pfn_mapped
> right ?
>
> So, the first page allocated by alloc_low_pages() is not on local node,
> right ?
It is from BRK with kernel code.
> Furthermore, the first page of pagetable is not on local node, right ?
It is in BRK for node with start = 0.
Other node, it is from low_range aka node with start = 0.
Thanks
Yinghai
--
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