On Wed, Jun 20, 2007 at 06:03:02AM -0700, Arjan van de Ven wrote: > 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....
Today PF_MEMALLOC doesn't do much in interrupt context. If PF_MEMALLOC is the right usage model for this, then we need to fix the behavior of PF_MEMALLOC in the interrupt context(for our usage model, we do most of the allocations in interrupt context). I am not very familiar with PF_MEMALLOC. So experts please comment. thanks, suresh - 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/
