[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <op.vxgu7zgo3l0zgt@mnazarewicz-glaptop>
Date: Wed, 22 Jun 2011 09:32:13 +0200
From: "Michal Nazarewicz" <mina86@...a86.com>
To: linaro-mm-sig@...ts.linaro.org, "Hans Verkuil" <hverkuil@...all.nl>
Cc: "Arnd Bergmann" <arnd@...db.de>,
linux-arm-kernel@...ts.infradead.org,
"'Daniel Walker'" <dwalker@...eaurora.org>, linux-mm@...ck.org,
"'Mel Gorman'" <mel@....ul.ie>, linux-kernel@...r.kernel.org,
"'Jesse Barker'" <jesse.barker@...aro.org>,
"'Kyungmin Park'" <kyungmin.park@...sung.com>,
"'Ankita Garg'" <ankita@...ibm.com>,
"'Andrew Morton'" <akpm@...ux-foundation.org>,
linux-media@...r.kernel.org,
"'KAMEZAWA Hiroyuki'" <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [Linaro-mm-sig] [PATCH 08/10] mm: cma: Contiguous Memory
Allocator added
On Wed, 22 Jun 2011 09:03:30 +0200, Hans Verkuil <hverkuil@...all.nl>
wrote:
> What I was wondering about is how this patch series changes the
> allocation in case it can't allocate from the CMA pool. Will it
> attempt to fall back to a 'normal' allocation?
Unless Marek changed something since I wrote the code, which I doubt,
if CMA cannot obtain memory from CMA region, it will fail.
Part of the reason is that CMA lacks the knowledge where to allocate
memory from. For instance, with the case of several memory banks,
it does not know which memory bank to allocate from.
It is, in my opinion, a task for a higher level functions (read:
DMA layer) to try another mechanism if CMA fails.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michal "mina86" Nazarewicz (o o)
ooo +-----<email/xmpp: mnazarewicz@...gle.com>-----ooO--(_)--Ooo--
--
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