Re: [PATCH/RFCv4 0/6] The Contiguous Memory Allocator framework

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 26, 2010 at 1:06 PM, Minchan Kim <minchan.kim@xxxxxxxxx> wrote:
> On Thu, Aug 26, 2010 at 12:44 PM, KAMEZAWA Hiroyuki
> <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
>> On Thu, 26 Aug 2010 11:50:17 +0900
>> KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
>>
>>> 128MB...too big ? But it's depend on config.
>>>
>>> IBM's ppc guys used 16MB section, and recently, a new interface to shrink
>>> the number of /sys files are added, maybe usable.
>>>
>>> Something good with this approach will be you can create "cma" memory
>>> before installing driver.
>>>
>>> But yes, complicated and need some works.
>>>
>> Ah, I need to clarify what I want to say.
>>
>> With compaction, it's helpful, but you can't get contiguous memory larger
>> than MAX_ORDER, I think. To get memory larger than MAX_ORDER on demand,
>> memory hot-plug code has almost all necessary things.
>
> True. Doesn't patch's idea of Christoph helps this ?
> http://lwn.net/Articles/200699/

Of course, It itself can't meet our requirement but idea of range
allocation seem to be good.
I think it can be start point.

>
> --
> Kind regards,
> Minchan Kim
>



-- 
Kind regards,
Minchan Kim
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux