[PATCHv8 00/12] Contiguous Memory Allocator
mina86 at mina86.com
Thu Dec 23 10:02:07 EST 2010
>> On Thu, Dec 23, 2010 at 03:04:07PM +0100, Tomasz Fujak wrote:
>>> In other words, should we take your response as yet another NAK?
>>> Or would you try harder and at least point us to some direction that
>>> would not doom the effort from the very beginning.
> On Thu, Dec 23, 2010 at 4:16 PM, Russell King - ARM Linux
> <linux at arm.linux.org.uk> wrote:
>> What the fsck do you think I've been doing? This is NOT THE FIRST time
>> I've raised this issue. I gave up raising it after the first couple
>> of attempts because I wasn't being listened to.
>> You say about _me_ not being very helpful. How about the CMA proponents
>> start taking the issue I've raised seriously, and try to work out how
>> to solve it? And how about blaming them for the months of wasted time
>> on this issue _because_ _they_ have chosen to ignore it?
Felipe Contreras <felipe.contreras at gmail.com> writes:
> I've also raised the issue for ARM. However, I don't see what is the
> big problem.
> 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,
Having exactly that usage in mind, in v8 I've added notion of private
CMA contexts which can be used for DMA coherent RAM as well as memory
> and take chunks out of it until there's no more, and then return
> errors. That would work for ARM.
Best regards, _ _
.o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michal "mina86" Nazarewicz (o o)
More information about the linux-arm-kernel