[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201013211610.GA27034@alpha.franken.de>
Date: Tue, 13 Oct 2020 23:16:10 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Jinyang He <hejinyang@...ngson.cn>
Cc: Huacai Chen <chenhc@...ote.com>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: Add set_memory_node()
On Tue, Oct 13, 2020 at 11:19:43AM +0800, Jinyang He wrote:
> Commit e7ae8d174eec ("MIPS: replace add_memory_region with memblock")
this commit just changed code and doesn't change the problem you want to
solve.
> replaced add_memory_region(, , BOOT_MEM_RAM) with memblock_add(). But
> it doesn't work well on some platforms which have NUMA like Loongson64.
> Because memblock_add() calls memblock_add_range() and sets memory at
> MAX_NUMNODES. As mm/memblock.c says, assign the region to a NUMA node
> later by using memblock_set_node(). This patch provides a NUMA port
so it says later, which doesn't have to be right after the memblock_add.
I don't know why you need the whole mem=/memmap= game, but please do a
for_each_memblock(...)
memblock_set_node(...);
somewhere in arch/mips/loongson64 to fix up the memory blocks as needed.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists