Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls

On Tue, 19 Jun 2007, Keshavamurthy, Anil S wrote:

> So far in our test scenario, we were unable to create
> any memory allocation failure inside dma map api calls.

All these functions should have gfp_t flags passed to them.
Otherwise you are locked into the use of GFP_ATOMIC. If this is a 
parameter then you may be able to use GFP_KERNEL in various places and you 
may develop the code to have less GFP_ATOMIC allocs in the future.

-
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: Arjan van de Ven <[email protected]>

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]>

Prev by Date: Re: Fix signalfd interaction with thread-private signals
Next by Date: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
Previous by thread: [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):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]