[lkml]   [2007]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
    Intel IOMMU driver needs memory during DMA map calls to setup its internal
    page tables and for other data structures. As we all know that these DMA
    map calls are mostly called in the interrupt context or with the spinlock
    held by the upper level drivers(network/storage drivers), so in order to
    avoid any memory allocation failure due to low memory issues,
    this patch makes memory allocation by temporarily setting PF_MEMALLOC
    flags for the current task before making memory allocation calls.

    We evaluated mempools as a backup when kmem_cache_alloc() fails
    and found that mempools are really not useful here because
    1) We don;t know for sure how much to reserve in advance
    2) And mempools are not useful for GFP_ATOMIC case (as we call
    memory alloc functions with GFP_ATOMIC)

    With PF_MEMALLOC flag set in the current->flags, the VM subsystem avoids
    any watermark checks before allocating memory thus guarantee'ing the
    memory till the last free page. Further, looking at the code in
    mm/page_alloc.c in __alloc_pages() function, looks like this
    flag is useful only in the non-interrupt context.

    If we are in the interrupt context and memory allocation in IOMMU
    driver fails for some reason, then the DMA map api's will return
    failure and it is up to the higher level drivers to retry. Suppose,
    if upper level driver programs the controller with the buggy
    DMA virtual address, the IOMMU will block that DMA transaction
    when that happens thus preventing any corruption to main memory.

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

    Signed-off-by: Anil S Keshavamurthy <>

    drivers/pci/intel-iommu.c | 30 ++++++++++++++++++++++++++----
    1 file changed, 26 insertions(+), 4 deletions(-)

    Index: linux-2.6.22-rc4-mm2/drivers/pci/intel-iommu.c
    --- linux-2.6.22-rc4-mm2.orig/drivers/pci/intel-iommu.c 2007-06-18 15:45:46.000000000 -0700
    +++ linux-2.6.22-rc4-mm2/drivers/pci/intel-iommu.c 2007-06-19 13:10:29.000000000 -0700
    @@ -84,9 +84,31 @@
    static struct kmem_cache *iommu_devinfo_cache;
    static struct kmem_cache *iommu_iova_cache;

    +static inline void *iommu_kmem_cache_alloc(struct kmem_cache *cachep)
    + unsigned int flags;
    + void *vaddr;
    + /* trying to avoid low memory issues */
    + flags = current->flags & PF_MEMALLOC;
    + current->flags |= PF_MEMALLOC;
    + vaddr = kmem_cache_alloc(cachep, GFP_ATOMIC);
    + current->flags &= (~PF_MEMALLOC | flags);
    + return vaddr;
    static inline void *alloc_pgtable_page(void)
    - return (void *)get_zeroed_page(GFP_ATOMIC);
    + unsigned int flags;
    + void *vaddr;
    + /* trying to avoid low memory issues */
    + flags = current->flags & PF_MEMALLOC;
    + current->flags |= PF_MEMALLOC;
    + vaddr = (void *)get_zeroed_page(GFP_ATOMIC);
    + current->flags &= (~PF_MEMALLOC | flags);
    + return vaddr;

    static inline void free_pgtable_page(void *vaddr)
    @@ -96,7 +118,7 @@

    static inline void *alloc_domain_mem(void)
    - return kmem_cache_alloc(iommu_domain_cache, GFP_ATOMIC);
    + return iommu_kmem_cache_alloc(iommu_domain_cache);

    static inline void free_domain_mem(void *vaddr)
    @@ -106,7 +128,7 @@

    static inline void * alloc_devinfo_mem(void)
    - return kmem_cache_alloc(iommu_devinfo_cache, GFP_ATOMIC);
    + return iommu_kmem_cache_alloc(iommu_devinfo_cache);

    static inline void free_devinfo_mem(void *vaddr)
    @@ -116,7 +138,7 @@

    struct iova *alloc_iova_mem(void)
    - return kmem_cache_alloc(iommu_iova_cache, GFP_ATOMIC);
    + return iommu_kmem_cache_alloc(iommu_iova_cache);

    void free_iova_mem(struct iova *iova)
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-06-20 00:23    [W:0.042 / U:6.160 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site