aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include
diff options
context:
space:
mode:
authorMarek Szyprowski <m.szyprowski@samsung.com>2012-11-07 15:37:07 +0100
committerMarek Szyprowski <m.szyprowski@samsung.com>2012-12-11 09:28:08 +0100
commit387870f2d6d679746020fa8e25ef786ff338dc98 (patch)
tree3faebf54631b06febae94f7d626370e8250d9526 /include
parentLinux 3.7 (diff)
downloadwireguard-linux-387870f2d6d679746020fa8e25ef786ff338dc98.tar.xz
wireguard-linux-387870f2d6d679746020fa8e25ef786ff338dc98.zip
mm: dmapool: use provided gfp flags for all dma_alloc_coherent() calls
dmapool always calls dma_alloc_coherent() with GFP_ATOMIC flag, regardless the flags provided by the caller. This causes excessive pruning of emergency memory pools without any good reason. Additionaly, on ARM architecture any driver which is using dmapools will sooner or later trigger the following error: "ERROR: 256 KiB atomic DMA coherent pool is too small! Please increase it with coherent_pool= kernel parameter!". Increasing the coherent pool size usually doesn't help much and only delays such error, because all GFP_ATOMIC DMA allocations are always served from the special, very limited memory pool. This patch changes the dmapool code to correctly use gfp flags provided by the dmapool caller. Reported-by: Soeren Moch <smoch@web.de> Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> Tested-by: Andrew Lunn <andrew@lunn.ch> Tested-by: Soeren Moch <smoch@web.de> Cc: stable@vger.kernel.org
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions