summaryrefslogtreecommitdiffstats
path: root/usr/Kconfig
diff options
context:
space:
mode:
authorFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>2008-09-08 18:10:10 +0900
committerIngo Molnar <mingo@elte.hu>2008-09-08 15:50:05 +0200
commit3a80b6aa271eb08a3da1a04b5cbdcdc19d4a5ae0 (patch)
tree764dff7d96293683ad4066c3e0c7631299c6f470 /usr/Kconfig
parente51af6630848406fc97adbd71443818cdcda297b (diff)
downloadop-kernel-dev-3a80b6aa271eb08a3da1a04b5cbdcdc19d4a5ae0.zip
op-kernel-dev-3a80b6aa271eb08a3da1a04b5cbdcdc19d4a5ae0.tar.gz
ia64: dma_alloc_coherent always use GFP_DMA
This patch makes dma_alloc_coherent use GFP_DMA at all times. This is necessary for swiotlb, which requires the callers to set up the gfp flags properly. swiotlb_alloc_coherent tries to allocate pages with the gfp flags. If the allocated memory isn't fit for dev->coherent_dma_mask, swiotlb_alloc_coherent reserves some of the swiotlb memory area, which is precious resource. So the callers need to set up the gfp flags properly. This patch means that other IA64 IOMMUs' dma_alloc_coherent also use GFP_DMA. These IOMMUs (e.g. SBA IOMMU) don't need GFP_DMA since they can map a memory to any address. But IA64's GFP_DMA is large, generally drivers allocate small memory with dma_alloc_coherent only at startup. So I chose the simplest way to set up the gfp flags for swiotlb. Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Acked-by: Joerg Roedel <joerg.roedel@amd.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'usr/Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud