From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail137.messagelabs.com (mail137.messagelabs.com [216.82.249.19]) by kanga.kvack.org (Postfix) with SMTP id BDAA16B0093 for ; Thu, 23 Dec 2010 10:02:13 -0500 (EST) Received: by fxm12 with SMTP id 12so557798fxm.14 for ; Thu, 23 Dec 2010 07:02:11 -0800 (PST) From: Michal Nazarewicz Subject: Re: [PATCHv8 00/12] Contiguous Memory Allocator 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> Date: Thu, 23 Dec 2010 16:02:07 +0100 In-Reply-To: (Felipe Contreras's message of "Thu, 23 Dec 2010 16:42:57 +0200") Message-ID: <87d3osedn4.fsf@erwin.mina86.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: owner-linux-mm@kvack.org To: Felipe Contreras Cc: Russell King - ARM Linux , Tomasz Fujak , Marek Szyprowski , Daniel Walker , Kyungmin Park , Mel Gorman , KAMEZAWA Hiroyuki , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, Andrew Morton , linux-media@vger.kernel.org, Johan MOSSBERG , Ankita Garg List-ID: >> 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 > wrote: >> What the fsck do you think I've been doing? =C2=A0This is NOT THE FIRST = time >> I've raised this issue. =C2=A0I 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. =C2=A0How about the CMA propo= nents >> start taking the issue I've raised seriously, and try to work out how >> to solve it? =C2=A0And how about blaming them for the months of wasted t= ime >> on this issue _because_ _they_ have chosen to ignore it? Felipe Contreras 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,=20 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 mapped devices. > and take chunks out of it until there's no more, and then return > errors. That would work for ARM. --=20 Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=3D./ `o ..o | Computer Science, Michal "mina86" Nazarewicz (o o) ooo +------ooO--(_)--Ooo-- -- 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/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: email@kvack.org