From: davidb@codeaurora.org (David Brown) Date: Thu, 23 Dec 2010 10:04:51 -0800 Subject: [PATCHv8 00/12] Contiguous Memory Allocator In-Reply-To: (Felipe Contreras's message of "Thu, 23 Dec 2010 16:42:57 +0200") References: <20101223100642.GD3636@n2100.arm.linux.org.uk> <00ea01cba290$4d67f500$e837df00$%szyprowski@samsung.com> <20101223121917.GG3636@n2100.arm.linux.org.uk> <4D135004.3070904@samsung.com> <20101223134838.GK3636@n2100.arm.linux.org.uk> <4D1356D7.2000008@samsung.com> <20101223141608.GM3636@n2100.arm.linux.org.uk> Message-ID: <8yasjxobc1o.fsf@huya.qualcomm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Felipe Contreras 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.