From: David Miller <davem@davemloft.net>
To: sam@ravnborg.org
Cc: yinghai@kernel.org, tj@kernel.org, mhocko@suse.cz,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Weirdness in __alloc_bootmem_node_high
Date: Sun, 22 Apr 2012 15:22:10 -0400 (EDT) [thread overview]
Message-ID: <20120422.152210.1520263792125579554.davem@davemloft.net> (raw)
In-Reply-To: <20120420194309.GA3689@merkur.ravnborg.org>
From: Sam Ravnborg <sam@ravnborg.org>
Date: Fri, 20 Apr 2012 21:43:09 +0200
> I have it almost finished - except that it does not work :-(
> We have limitations in what area we can allocate very early,
> and here I had to use the alloc_bootmem_low() variant.
> I had preferred a variant that allowed me to allocate
> bottom-up in this case.
I think you're going to have to bear down and map all of linear kernel
mappings before you start using the bootmem code rather than
afterwards.
--
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-22 19:22 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
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 [this message]
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=20120422.152210.1520263792125579554.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=sam@ravnborg.org \
--cc=tj@kernel.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).