On Mon, Nov 12, 2012 at 10:48:02AM +0100, Soeren Moch wrote:

On 11.11.2012 18:22, Andrew Lunn wrote:

quoted

On Thu, Nov 08, 2012 at 07:38:57AM +0100, Marek Szyprowski wrote:

quoted

dmapool always calls dma_alloc_coherent() with GFP_ATOMIC flag,

regardless

quoted

quoted

the flags provided by the caller. This causes excessive pruning of
emergency memory pools without any good reason. This patch

changes the code

quoted

quoted

to correctly use gfp flags provided by the dmapool caller. This should
solve the dmapool usage on ARM architecture, where GFP_ATOMIC DMA
allocations can be served only from the special, very limited

memory pool.

quoted

quoted

Reported-by: Soren Moch <redacted>

Please use
Reported-by: Soeren Moch <redacted>

quoted

quoted

Reported-by: Thomas Petazzoni <redacted>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>

Tested-by: Andrew Lunn <andrew@lunn.ch>

I tested this on a Kirkwood QNAP after removing the call to
init_dma_coherent_pool_size().

    Andrew

Tested-by: Soeren Moch <redacted>

Now I had a chance to test this patch on my Kirkwood guruplug
system with linux-3.6.6 . It is running much better now, but with the
original 256K coherent pool size I still see errors after several hours
of runtime:

Nov 12 09:42:32 guru kernel: ERROR: 256 KiB atomic DMA coherent pool
is too small!
Nov 12 09:42:32 guru kernel: Please increase it with coherent_pool=
kernel parameter!

Hi Soeren

Could you tell us what DVB devices you are using.

Thanks
	Andrew