[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080314113646.d73066f7.kamezawa.hiroyu@jp.fujitsu.com>
Date: Fri, 14 Mar 2008 11:36:46 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: "Yinghai Lu" <yhlu.kernel@...il.com>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"Ingo Molnar" <mingo@...e.hu>, "Andi Kleen" <ak@...e.de>,
"Christoph Lameter" <clameter@....com>,
linux-kernel@...r.kernel.org,
"Yasunori Goto" <y-goto@...fujitsu.com>
Subject: Re: [PATCH] mm: make reserve_bootmem can crossed the nodes
On Thu, 13 Mar 2008 19:00:33 -0700
"Yinghai Lu" <yhlu.kernel@...il.com> wrote:
> > Hmm, can a call to reserve_bootmem() return a memory region which spread across
> > prural nodes ?
>
> Yes. there is one reserve_bootmem in reserve_crashkernel. and position
> is passed via commandline...
> there is some chance for ramdisk too. it is called via reserve_bootmem_generic.
>
Hmm, ok. I finally see your point.
please allow me to make clarification
Background:
- reserve_bootmem is called for *reserve* memory before bootmem allocator.
- It specifies <address, size>.
- Because <addrees, size> are argments, memory hole in <address, size> is not
problem here.
Before change,
- reseve_bootmem() only works for Node(0)
After change
- reserve_bootmem() works on sutiable nodes for <address, size>
- It can spread accross among prural nodes.
thank you for your work.
Regards,
-Kame
--
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