[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8yasjxobc1o.fsf@huya.qualcomm.com>
Date: Thu, 23 Dec 2010 10:04:51 -0800
From: David Brown <davidb@...eaurora.org>
To: Felipe Contreras <felipe.contreras@...il.com>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
Ankita Garg <ankita@...ibm.com>,
Daniel Walker <dwalker@...eaurora.org>,
Kyungmin Park <kmpark@...radead.org>,
linux-media@...r.kernel.org,
Johan MOSSBERG <johan.xx.mossberg@...ricsson.com>,
Mel Gorman <mel@....ul.ie>, linux-kernel@...r.kernel.org,
Michal Nazarewicz <mina86@...a86.com>, linux-mm@...ck.org,
linux-arm-kernel@...ts.infradead.org,
Andrew Morton <akpm@...ux-foundation.org>,
Tomasz Fujak <t.fujak@...sung.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCHv8 00/12] Contiguous Memory Allocator
Felipe Contreras <felipe.contreras@...il.com> writes:
> On Thu, Dec 23, 2010 at 4:16 PM, Russell King - ARM Linux
> A generic solution (that I think I already proposed) would be to
> reserve a chunk of memory for the CMA that can be removed from the
> normally mapped kernel memory through memblock at boot time. The size
> of this memory region would be configurable through kconfig. Then, the
> CMA would have a "dma" flag or something, and take chunks out of it
> until there's no more, and then return errors. That would work for
> ARM.
That sounds an awful lot like the Android kernel's pmem implementation.
Solving this problem is important for us as well, but, I'm not sure I
see a better solution that something like Felipe suggests.
The disadvantage, of course, being that the memory isn't available for
the system when the user isn't doing the multi-media.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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