From: Felipe Contreras <felipe.contreras@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: andi@firstfloor.org, kamezawa.hiroyu@jp.fujitsu.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
minchan.kim@gmail.com
Subject: Re: [RFC][PATCH 1/3] contigous big page allocator
Date: Thu, 14 Oct 2010 15:09:13 +0300 [thread overview]
Message-ID: <AANLkTin-8mjL_B8g9cPoviQU0FUaEyb_v5_Fm4kbSweA@mail.gmail.com> (raw)
In-Reply-To: <20101014160217N.fujita.tomonori@lab.ntt.co.jp>
On Thu, Oct 14, 2010 at 10:07 AM, FUJITA Tomonori
<fujita.tomonori@lab.ntt.co.jp> wrote:
> On Wed, 13 Oct 2010 09:01:43 +0200
> Andi Kleen <andi@firstfloor.org> wrote:
>
>> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
>> >
>> > What this wants to do:
>> > allocates a contiguous chunk of pages larger than MAX_ORDER.
>> > for device drivers (camera? etc..)
>>
>> I think to really move forward you need a concrete use case
>> actually implemented in tree.
>
> As already pointed out, some embeded drivers need physcailly
> contignous memory. Currenlty, they use hacky tricks (e.g. playing with
> the boot memory allocators). There are several proposals for this like
> adding a new kernel memory allocator (from samsung).
>
> It's ideal if the memory allocator can handle this, I think.
Not only contiguous, but sometimes also coherent.
--
Felipe Contreras
--
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:[~2010-10-14 12:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 3:15 KAMEZAWA Hiroyuki
2010-10-13 3:17 ` [RFC][PATCH 2/3] find a contiguous range KAMEZAWA Hiroyuki
2010-10-17 3:18 ` Minchan Kim
2010-10-18 0:29 ` KAMEZAWA Hiroyuki
2010-10-13 3:18 ` [RFC][PATCH 3/3] alloc contig pages with migration KAMEZAWA Hiroyuki
2010-10-17 4:05 ` Minchan Kim
2010-10-18 0:35 ` KAMEZAWA Hiroyuki
2010-10-18 5:18 ` Minchan Kim
2010-10-18 5:31 ` KAMEZAWA Hiroyuki
2010-10-18 5:52 ` Minchan Kim
2010-10-18 5:52 ` KAMEZAWA Hiroyuki
2010-10-13 5:05 ` [RFC][PATCH 1/3] contigous big page allocator KOSAKI Motohiro
2010-10-13 7:01 ` Andi Kleen
2010-10-13 7:12 ` KAMEZAWA Hiroyuki
2010-10-13 8:36 ` Andi Kleen
2010-10-13 8:39 ` KAMEZAWA Hiroyuki
2010-10-14 1:59 ` KOSAKI Motohiro
2010-10-14 7:07 ` FUJITA Tomonori
2010-10-14 7:24 ` Andi Kleen
2010-10-14 8:36 ` FUJITA Tomonori
2010-10-14 12:55 ` Andi Kleen
2010-10-14 15:09 ` FUJITA Tomonori
2010-10-14 12:10 ` Felipe Contreras
2010-10-14 12:09 ` Felipe Contreras [this message]
2010-10-14 15:24 ` FUJITA Tomonori
2010-10-14 21:50 ` Felipe Contreras
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=AANLkTin-8mjL_B8g9cPoviQU0FUaEyb_v5_Fm4kbSweA@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=andi@firstfloor.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@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