linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Weirdness in __alloc_bootmem_node_high
Date: Tue, 17 Apr 2012 11:07:10 -0700	[thread overview]
Message-ID: <CAE9FiQXvZ4eSCwMSG2H7CC6suQe37TmQpmOEKW_082W3zz-6Fw@mail.gmail.com> (raw)
In-Reply-To: <20120417173203.GA32482@tiehlicka.suse.cz>

On Tue, Apr 17, 2012 at 10:32 AM, Michal Hocko <mhocko@suse.cz> wrote:
> On Tue 17-04-12 10:12:30, Yinghai Lu wrote:
>>
>> We are not using bootmem with x86 now, so could remove those workaround now.
>
> Could you be more specific about what the workaround is used for?

Don't bootmem allocating too low to use up all low memory. like for
system with lots of memory for sparse vmemmap.

when nobootmem.c is used, __alloc_bootmem_node_high is the same as
__alloc_bootmem_node.

Thanks

Yinghai

--
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>

  reply	other threads:[~2012-04-17 18:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 15:55 Michal Hocko
2012-04-17 17:12 ` Yinghai Lu
2012-04-17 17:32   ` Michal Hocko
2012-04-17 18:07     ` Yinghai Lu [this message]
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
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=CAE9FiQXvZ4eSCwMSG2H7CC6suQe37TmQpmOEKW_082W3zz-6Fw@mail.gmail.com \
    --to=yinghai@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    /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