Re: dma_alloc_coherent fragmentation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Nishant,

From: "ext Kamat, Nishant" <nskamat@xxxxxx>
Subject: dma_alloc_coherent fragmentation
Date: Wed, 18 Mar 2009 14:03:45 +0100

> Forwarding on behalf of Nishanth Menon:
> 
> -----Original Message-----
> From: Menon, Nishanth 
> Sent: Tuesday, March 17, 2009 8:17 AM
> To: 'linux-arm-kernel@xxxxxxxxxxxxxxxxxxxxxx'
> Cc: Gupta, Ramesh; Kevin Hilman; linux-omap@xxxxxxxxxxxxxxx; Ramirez Luna, Omar; Kanigeri, Hari; Ameya Palande; Guzman Lugo, Fernando; Ameya Palande
> Subject: dma_alloc_coherent fragmentation
> 
> Looping in linux-arm ML:
> 
> Discussion Ref: [1](linux-omap mailing list)
> While working with Linux OMAP kernel[2] we found that on allocating
> 4 meg chunks using dma_alloc_coherent and de-allocating with
> dma_free_coherent in a loop using a test driver[7], the memory is
> getting fragmented as shown by Ameya's observation [3] finally
> resulting in dump_stack due to lack of pages.

What would happen with __GFP_RECLAIMABLE for dma_alloc_coherent()?
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux