From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"Kleen, Andi" <andi.kleen@intel.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
Bob Liu <lliubbo@gmail.com>,
"fujita.tomonori@lab.ntt.co.jp" <fujita.tomonori@lab.ntt.co.jp>,
"pawel@osciak.com" <pawel@osciak.com>,
"felipe.contreras@gmail.com" <felipe.contreras@gmail.com>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [PATCH 0/4] big chunk memory allocator v4
Date: Tue, 23 Nov 2010 16:44:11 +0100 [thread overview]
Message-ID: <op.vmmrbxp57p4s8u@pikus> (raw)
In-Reply-To: <F4DF93C7785E2549970341072BC32CD796018FCB@irsmsx503.ger.corp.intel.com>
On Mon, 22 Nov 2010 09:59:57 +0100, Kleen, Andi <andi.kleen@intel.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, 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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-11-23 15:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 8:10 [PATCH 0/4] big chunk memory allocator v4 KAMEZAWA Hiroyuki
2010-11-19 8:12 ` [PATCH 1/4] alloc_contig_pages() move some functions to page_isolation.c KAMEZAWA Hiroyuki
2010-11-21 15:07 ` Minchan Kim
2010-11-19 8:14 ` [PATCH 2/4] alloc_contig_pages() find appropriate physical memory range KAMEZAWA Hiroyuki
2010-11-21 15:21 ` Minchan Kim
2010-11-22 0:11 ` KAMEZAWA Hiroyuki
2010-11-22 11:20 ` Minchan Kim
2010-11-24 0:15 ` KAMEZAWA Hiroyuki
2010-11-19 8:15 ` [PATCH 3/4] alloc_contig_pages() allocate big chunk memory using migration KAMEZAWA Hiroyuki
2010-11-21 15:25 ` Minchan Kim
2010-11-22 0:13 ` KAMEZAWA Hiroyuki
2010-11-22 11:44 ` Minchan Kim
2010-11-24 0:20 ` KAMEZAWA Hiroyuki
2010-11-19 8:16 ` [PATCH 4/4] alloc_contig_pages() use better allocation function for migration KAMEZAWA Hiroyuki
2010-11-22 12:01 ` Minchan Kim
2010-11-19 20:56 ` [PATCH 0/4] big chunk memory allocator v4 Andrew Morton
2010-11-22 0:04 ` KAMEZAWA Hiroyuki
2010-11-23 15:46 ` Michał Nazarewicz
2010-11-24 0:36 ` KAMEZAWA Hiroyuki
2010-11-22 0:30 ` Felipe Contreras
2010-11-22 8:59 ` Kleen, Andi
2010-11-23 15:44 ` Michał Nazarewicz [this message]
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=op.vmmrbxp57p4s8u@pikus \
--to=m.nazarewicz@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=felipe.contreras@gmail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=minchan.kim@gmail.com \
--cc=pawel@osciak.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;
as well as URLs for NNTP newsgroup(s).