From: Linus Torvalds <torvalds@linux-foundation.org>
To: Johannes Weiner <hannes@saeurebad.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
Yinghai Lu <yhlu.kernel@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Yasunori Goto <y-goto@jp.fujitsu.com>
Subject: Re: [rfc][patch 0/3] bootmem2: a memory block-oriented boot time allocator
Date: Mon, 5 May 2008 08:23:34 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805050820000.32269@woody.linux-foundation.org> (raw)
In-Reply-To: <20080505095938.326928514@symbol.fehenstaub.lan>
On Mon, 5 May 2008, Johannes Weiner wrote:
>
> here is a bootmem allocator replacement that uses one bitmap for all
> available pages and works with a model of contiguous memory blocks
> that reside on nodes instead of nodes only as the current allocator
> does.
Won't this have problems with huge non-contiguous areas?
Some setups have traditionally had node memory separated in physical space
by the high bits of the memory address, and using a single bitmap for such
things would potentially be basically impossible - even with a single bit
per page, the "span" of possible pages is potentially just too high, even
if the nodes themselves don't have tons of memory, because the memory is
just very spread out - and allocating the initial bitmap may not work
reliably.
Now, admittedly I don't know if we even support that kind of thing or if
people really do things that way any more, so maybe it's not an issue.
Linus
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-05-05 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 9:59 Johannes Weiner
2008-05-05 9:59 ` [rfc][patch 1/3] mm: Define NR_NODE_MEMBLKS unconditionally Johannes Weiner
2008-05-05 9:59 ` [rfc][patch 2/3] mm: bootmem2 - memory block oriented boot time allocator Johannes Weiner
2008-05-05 9:59 ` [rfc][patch 3/3] x86: Use bootmem2 on x86_32 Johannes Weiner
2008-05-05 11:23 ` [rfc][patch 0/3] bootmem2: a memory block-oriented boot time allocator Johannes Weiner
2008-05-05 15:23 ` Linus Torvalds [this message]
2008-05-05 16:04 ` Robin Holt
2008-05-06 9:00 ` Johannes Weiner
2008-05-05 18:58 ` Andi Kleen
2008-05-06 8:57 ` Johannes Weiner
2008-05-07 12:29 ` [RFC no patch yet] bootmem2: Another try Johannes Weiner
2008-05-07 14:37 ` Linus Torvalds
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=alpine.LFD.1.10.0805050820000.32269@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hannes@saeurebad.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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