[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706111428410.20454@schroedinger.engr.sgi.com>
Date: Mon, 11 Jun 2007 14:29:56 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>
cc: Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, gregkh@...e.de, muli@...ibm.com,
asit.k.mallick@...el.com, suresh.b.siddha@...el.com,
arjan@...ux.intel.com, ashok.raj@...el.com, shaohua.li@...el.com,
davem@...emloft.net
Subject: Re: [Intel-IOMMU 02/10] Library routine for pre-allocat pool handling
On Mon, 11 Jun 2007, Keshavamurthy, Anil S wrote:
> Hence, can I assume that the conclusion of this
> discussion is to use kmem_cache_alloc() functions
> to allocate memory in dma_map_{single|sg} API's?
Use the page allocator for page size allocations. If you need to have
specially aligned memory in less than page sized chunks then use
kmem_cache_alloc with a specially configured slab.
>
> Again, if dma_map_{single|sg} API's fails due to
> failure to allocate memory, the only thing that can
> be done is to panic as this is what few of the other
> IOMMU implementation is doing today.
Why does it have to be so severe? The I/O operation fails right?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists