Peter Zijlstra wrote:
So a reclaim context (kswapd and direct reclaim) set PF_MEMALLOC to ensure they themselves will not block on a memory allocation. And it is understood that these code paths have a bounded memory footprint.
that's a too simplistic view though; what happens is that kswapd will queue the IO, but the irq context will then take the IO from the queue and do the DMA mapping... which needs the memory.....
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- From: Peter Zijlstra <[email protected]>
- Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- References:
- [Intel IOMMU 00/10] Intel IOMMU support, take #2
- From: "Keshavamurthy, Anil S" <[email protected]>
- [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- From: "Keshavamurthy, Anil S" <[email protected]>
- Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- From: Peter Zijlstra <[email protected]>
- Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- From: Arjan van de Ven <[email protected]>
- Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- From: "Siddha, Suresh B" <[email protected]>
- Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- From: Peter Zijlstra <[email protected]>
- [Intel IOMMU 00/10] Intel IOMMU support, take #2
- Prev by Date: [patch] exclude sync signals from signalfd sets
- Next by Date: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Previous by thread: Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- Next by thread: Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- Index(es):
 |