From: Tejun Heo <tj@kernel.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Yinghai Lu <yinghai@kernel.org>, Michal Hocko <mhocko@suse.cz>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Weirdness in __alloc_bootmem_node_high
Date: Tue, 17 Apr 2012 14:33:13 -0700 [thread overview]
Message-ID: <20120417213313.GC19975@google.com> (raw)
In-Reply-To: <20120417183042.GA21051@merkur.ravnborg.org>
Hello, Sam.
On Tue, Apr 17, 2012 at 08:30:42PM +0200, Sam Ravnborg wrote:
> It would be nice if someone familiar with the memblock/bootmem
> internals could cleans up the leftovers from the migration
> of x86 to memblock / nobootmem.
>
> This would be less to be confused about when other migrate to
> use memblock.
I can't remember the details now (my memory sucks big time) but there
were some obstacles and I decided to defer cleaning up. I'm kinda
overwhelmed in other areas so if anyone is interested in cleaning up,
I'll be happy to help. If not, I'll try to get to it.
Thanks.
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-17 21:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 15:55 Weirdness in __alloc_bootmem_node_high Michal Hocko
2012-04-17 17:12 ` Yinghai Lu
2012-04-17 17:32 ` Michal Hocko
2012-04-17 18:07 ` Yinghai Lu
2012-04-17 18:30 ` Sam Ravnborg
2012-04-17 21:33 ` Tejun Heo [this message]
2012-04-19 12:50 ` Michal Hocko
2012-04-20 18:29 ` Tejun Heo
2012-04-20 19:14 ` Sam Ravnborg
2012-04-20 19:29 ` Michal Hocko
2012-04-20 19:32 ` Yinghai Lu
2012-04-20 19:41 ` Michal Hocko
2012-04-20 19:30 ` Yinghai Lu
2012-04-20 19:43 ` Sam Ravnborg
2012-04-22 19:22 ` David Miller
2012-04-22 20:05 ` Sam Ravnborg
2012-04-23 2:00 ` David Miller
2012-04-23 5:12 ` Sam Ravnborg
2012-04-24 6:32 ` Sam Ravnborg
2012-04-24 7:00 ` David Miller
2012-04-27 3:32 ` David Miller
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=20120417213313.GC19975@google.com \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=sam@ravnborg.org \
--cc=yinghai@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).