DMA pool is better solution for such usecases.
> -----Original Message-----
> From: linux-omap-ow...@vger.kernel.org
> [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of pramod gurav
> Sent: Wednesday, April 22, 2009 1:17 PM
> To: Menon, Nishanth
> Cc: linux-omap@vger.kernel.org
> Subject: Re: dma_alloc_coherent fragmentation
>
> Hi Nishant,
> I am facing the same problem to allocate a chunk of 4MB on omap3evm
> using dma_alloc_coherent. I used the test driver mentioned here
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg11074.html
>
> I applied the patch for
> ioremap(24f11ec001920f1cfaeeed8e8b55725d900bbb56) suggested by
> Russell, but stiill seeing the error saying
>
> coherent allocation too big (requested 0x400000 mask 0xffffffff)
> alloc[0] - virt=0x00000000 phy=0xFFFFFFFF size=0x00400000
> Allocation failed idx=0
> insmod: cannot insert `dummy.ko': Cannot allocate memory (-1): Cannot
> allocate memory
>
> I changed the GFP_KERNEL to GFP_TEMPORARY and also to (GFP_KERNEL |
> __GFP_RECLAIMABLE), but failed to insmod the module.
> I am working on linux-omap 2.6.28 kernel. Even I could not allocate
> memory size greater than 1MB.
> Has this been fixed? Are there any patches to fix this issue?
>
> On Thu, Mar 19, 2009 at 2:36 PM, Menon, Nishanth <n...@ti.com> wrote:
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
