On Mon, Nov 12, 2012 at 10:48:02AM +0100, Soeren Moch wrote:On 11.11.2012 18:22, Andrew Lunn wrote:Hi SoerenOn Thu, Nov 08, 2012 at 07:38:57AM +0100, Marek Szyprowski wrote:regardlessdmapool always calls dma_alloc_coherent() with GFP_ATOMIC flag,changes the codethe flags provided by the caller. This causes excessive pruning of
emergency memory pools without any good reason. This patch
memory pool.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
Please useReported-by: Soren Moch <smoch@xxxxxx>
Reported-by: Soeren Moch <smoch@xxxxxx>
Tested-by: Soeren Moch <smoch@xxxxxx>Reported-by: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>Tested-by: Andrew Lunn <andrew@xxxxxxx>
Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
I tested this on a Kirkwood QNAP after removing the call to
init_dma_coherent_pool_size().
Andrew
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!
Could you tell us what DVB devices you are using.
Thanks
Andrew