From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: mingo@elte.hu, clameter@sgi.com, linux-kernel@vger.kernel.org,
ak@suse.de, y-goto@jp.fujitsu.com,
kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [PATCH] mm: make free_bootmem to loop bdata_list
Date: Thu, 13 Mar 2008 12:10:58 -0700 [thread overview]
Message-ID: <86802c440803131210x5c2d826qe73b6ed37af2d835@mail.gmail.com> (raw)
In-Reply-To: <20080313120553.06fee622.akpm@linux-foundation.org>
On Thu, Mar 13, 2008 at 12:05 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
>
> On Thu, 13 Mar 2008 11:53:31 -0700
> "Yinghai Lu" <yhlu.kernel@gmail.com> wrote:
>
> > [PATCH] mm: make free_bootmem to loop bdata_list
> >
> > [PATCH] mm: fix boundary checking in free_bootmem_core
> >
> > make the free_bootmem_core could handle out of range case. we could use
> > bdata_list to make sure the range can be freed for sure.
> >
> > so next time, we don't need to loop online nodes and could use
> > free_bootmem directly.
> >
> > Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
> >
>
> What is the relationship (if any) between this and
> mm-fix-boundary-checking-in-free_bootmem_core.patch?
after mm-fix-boundary-checking-in-free_bootmem_core.patch, or you can
fold this into that.
>
> Do you believe ths new patch is needed in 2.6.25 and if so, why?
could solve some free_bootmem in extreme case like no ram on node 0.
YH
next prev parent reply other threads:[~2008-03-13 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 18:53 Yinghai Lu
2008-03-13 19:05 ` Andrew Morton
2008-03-13 19:10 ` Yinghai Lu [this message]
2008-03-14 1:39 ` KAMEZAWA Hiroyuki
2008-03-14 1:39 ` Yinghai Lu
2008-03-14 2:04 ` KAMEZAWA Hiroyuki
2008-03-14 2:07 ` Yinghai Lu
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=86802c440803131210x5c2d826qe73b6ed37af2d835@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--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 \
/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
all inboxes | Powered by JetHome®