[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <op.vmmrbxp57p4s8u@pikus>
Date: Tue, 23 Nov 2010 16:44:11 +0100
From: Michał Nazarewicz <m.nazarewicz@...sung.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
"Kleen, Andi" <andi.kleen@...el.com>
Cc: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"minchan.kim@...il.com" <minchan.kim@...il.com>,
Bob Liu <lliubbo@...il.com>,
"fujita.tomonori@....ntt.co.jp" <fujita.tomonori@....ntt.co.jp>,
"pawel@...iak.com" <pawel@...iak.com>,
"felipe.contreras@...il.com" <felipe.contreras@...il.com>,
"kosaki.motohiro@...fujitsu.com" <kosaki.motohiro@...fujitsu.com>
Subject: Re: [PATCH 0/4] big chunk memory allocator v4
On Mon, 22 Nov 2010 09:59:57 +0100, Kleen, Andi <andi.kleen@...el.com> wrote:
>> > But yes, because of fragmentation, this cannot guarantee 100%
>> alloc.
>> > If alloc_contig_pages() is called in system boot up or movable_zone
>> is used,
>> > this allocation succeeds at high rate.
>>
>> So this is an alternatve implementation for the functionality offered
>> by Michal's "The Contiguous Memory Allocator framework".
>
> I see them more as orthogonal: Michal's code relies on preallocation
> and manages the memory after that.
Yes and no. The v6 version adds not-yet-finished support for sharing
the preallocated blocks with page allocator (so if CMA is not using the
memory, page allocator can allocate it, and when CMA finally wants to
use it the allocated pages are migrated).
In the v6 implementation I have added a new migration type (I cannot seem
to find who proposed such approach first). When I'll end debugging the
code I'll try to work things out without adding additional entity (that
is new migration type).
--
Best regards, _ _
| Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o
| Computer Science, Michał "mina86" Nazarewicz (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists