[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <516377CF.2080004@cn.fujitsu.com>
Date: Tue, 09 Apr 2013 10:07:11 +0800
From: Lin Feng <linfeng@...fujitsu.com>
To: Will Deacon <will.deacon@....com>
CC: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"cl@...ux.com" <cl@...ux.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"hpa@...or.com" <hpa@...or.com>,
"yinghai@...nel.org" <yinghai@...nel.org>,
Catalin Marinas <Catalin.Marinas@....com>,
"arnd@...db.de" <arnd@...db.de>,
"tony@...mide.com" <tony@...mide.com>,
"ben@...adent.org.uk" <ben@...adent.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"isimatu.yasuaki@...fujitsu.com" <isimatu.yasuaki@...fujitsu.com>
Subject: Re: [PATCH 2/2] mm: vmemmap: arm64: add vmemmap_verify check for
hot-add node case
Hi will,
On 04/08/2013 06:55 PM, Will Deacon wrote:
> Given that we don't have NUMA support or memory-hotplug on arm64 yet, I'm
> not sure that this change makes much sense at the moment. early_pfn_to_nid
> will always return 0 and we only ever have one node.
>
> To be honest, I'm not sure what that vmemmap_verify check is trying to
> achieve anyway. ia64 does some funky node affinity initialisation early on
> but, for the rest of us, it looks like we always just check the distance
> from node 0.
Sorry for my noise to arm people.
Yes, not everyone cares about vmemmap_verify(), as you described it's not
necessary to arm64 at all.
thanks,
linfeng
--
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