public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@saeurebad.de>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Ingo Molnar" <mingo@elte.hu>, "Andi Kleen" <ak@suse.de>,
	"Christoph Lameter" <clameter@sgi.com>,
	linux-kernel@vger.kernel.org,
	"Yasunori Goto" <y-goto@jp.fujitsu.com>
Subject: Re: [PATCH] mm: make reserve_bootmem can crossed the nodes
Date: Sat, 15 Mar 2008 04:08:29 +0100	[thread overview]
Message-ID: <87fxus1y6q.fsf@saeurebad.de> (raw)
In-Reply-To: <86802c440803132003j4937546di1dc89cb51985cedb@mail.gmail.com> (Yinghai Lu's message of "Thu, 13 Mar 2008 20:03:37 -0700")

Hi,

"Yinghai Lu" <yhlu.kernel@gmail.com> writes:

> On Thu, Mar 13, 2008 at 7:58 PM, Johannes Weiner <hannes@saeurebad.de> wrote:
>> Hi,
>>
>>
>>  KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
>>
>>  > 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.
>>
>>  After the change it will iterate over all nodes, reserving the range
>>  `address to address+size' on each of them.
>
>  +     /* out of range */
>  +     if (addr >= bdata->node_boot_start && addr < bdata->last_success)
>  +             return;
>
> out of range will bail out...

Sorry, I did not see that.

	Hannes

      reply	other threads:[~2008-03-15  3:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 23:45 [PATCH] mm: make reserve_bootmem can crossed the nodes Yinghai Lu
2008-03-14  0:13 ` Johannes Weiner
2008-03-14  1:04   ` Yinghai Lu
2008-03-14  2:50     ` Johannes Weiner
2008-03-14  3:09       ` Yinghai Lu
2008-03-14  1:34 ` KAMEZAWA Hiroyuki
2008-03-14  1:35   ` Yinghai Lu
2008-03-14  1:55     ` KAMEZAWA Hiroyuki
2008-03-14  2:00       ` Yinghai Lu
2008-03-14  2:36         ` KAMEZAWA Hiroyuki
2008-03-14  2:58           ` Johannes Weiner
2008-03-14  3:03             ` Yinghai Lu
2008-03-15  3:08               ` Johannes Weiner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fxus1y6q.fsf@saeurebad.de \
    --to=hannes@saeurebad.de \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=y-goto@jp.fujitsu.com \
    --cc=yhlu.kernel@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox