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

Peter Zijlstra wrote:

PF_MEMALLOC as is, is meant to salvage the VM from the typical VM

deadlock.

.. and this IS the typical VM deadlock.. it is your storage driver trying to write out a piece of memory on behalf of the VM, and calls the iommu to map it, which then needs a bit of 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: "Siddha, Suresh B" <[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]>
  • Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
    • From: Peter Zijlstra <[email protected]>

• Prev by Date: Re: [perfmon] Re: [PATCH 1/2] Separate the performance counter allocation from the LAPIC NMI watchdog
• Next by Date: Re: [RFC PATCH 1/4] Union mount documentation.
• 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):
  • 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]