2013/11/23 H. Peter Anvin :
> On 11/22/2013 04:27 AM, Akinobu Mita wrote:
>>
>> I'm currently working for integrating DMA CMA with intel-iommu which
>> I can test. Regardless of which dma ops is actually used, I would
>> like to allocate large contiguous memory with dma_alloc_coherent()
>> and
2013/11/23 H. Peter Anvin h...@zytor.com:
On 11/22/2013 04:27 AM, Akinobu Mita wrote:
I'm currently working for integrating DMA CMA with intel-iommu which
I can test. Regardless of which dma ops is actually used, I would
like to allocate large contiguous memory with dma_alloc_coherent()
and
"H. Peter Anvin" writes:
>
> If you have a real iotlb, why would you need contiguous memory?
iotlb is often slow.
Another use case is allocating 1GB pages at runtime.
-Andi
--
a...@linux.intel.com -- Speaking for myself only
--
To unsubscribe from this list: send the line "unsubscribe
On 11/22/2013 04:27 AM, Akinobu Mita wrote:
>
> I'm currently working for integrating DMA CMA with intel-iommu which
> I can test. Regardless of which dma ops is actually used, I would
> like to allocate large contiguous memory with dma_alloc_coherent()
> and tell the base address to the device.
2013/11/22 H. Peter Anvin :
> On 11/21/2013 07:02 AM, Akinobu Mita wrote:
>>
>> I want to use DMA CMA for the feature that requires a single huge chunk
>> (about 64MB) of host memory.
>
> That is tautological. "I want to use the Contiguous Memory Allocator to
> allocate contiguous memory."
>
>>
Hello,
On 2013-11-20 00:32, Akinobu Mita wrote:
The DMA Contiguous Memory Allocator support on x86 is disabled when
swiotlb config option is enabled. So DMA CMA is always disabled on
x86_64 because swiotlb is always enabled. This attempts to support
for DMA CMA with enabling swiotlb config
Hello,
On 2013-11-20 00:32, Akinobu Mita wrote:
The DMA Contiguous Memory Allocator support on x86 is disabled when
swiotlb config option is enabled. So DMA CMA is always disabled on
x86_64 because swiotlb is always enabled. This attempts to support
for DMA CMA with enabling swiotlb config
2013/11/22 H. Peter Anvin h...@zytor.com:
On 11/21/2013 07:02 AM, Akinobu Mita wrote:
I want to use DMA CMA for the feature that requires a single huge chunk
(about 64MB) of host memory.
That is tautological. I want to use the Contiguous Memory Allocator to
allocate contiguous memory.
On 11/22/2013 04:27 AM, Akinobu Mita wrote:
I'm currently working for integrating DMA CMA with intel-iommu which
I can test. Regardless of which dma ops is actually used, I would
like to allocate large contiguous memory with dma_alloc_coherent()
and tell the base address to the device.
H. Peter Anvin h...@zytor.com writes:
If you have a real iotlb, why would you need contiguous memory?
iotlb is often slow.
Another use case is allocating 1GB pages at runtime.
-Andi
--
a...@linux.intel.com -- Speaking for myself only
--
To unsubscribe from this list: send the line
On 11/19/2013 03:32 PM, Akinobu Mita wrote:
> The DMA Contiguous Memory Allocator support on x86 is disabled when
> swiotlb config option is enabled. So DMA CMA is always disabled on
> x86_64 because swiotlb is always enabled. This attempts to support
> for DMA CMA with enabling swiotlb config
2013/11/20 Konrad Rzeszutek Wilk :
> On Wed, Nov 20, 2013 at 08:32:19AM +0900, Akinobu Mita wrote:
>> The DMA Contiguous Memory Allocator support on x86 is disabled when
>> swiotlb config option is enabled. So DMA CMA is always disabled on
>> x86_64 because swiotlb is always enabled. This
2013/11/20 Konrad Rzeszutek Wilk konrad.w...@oracle.com:
On Wed, Nov 20, 2013 at 08:32:19AM +0900, Akinobu Mita wrote:
The DMA Contiguous Memory Allocator support on x86 is disabled when
swiotlb config option is enabled. So DMA CMA is always disabled on
x86_64 because swiotlb is always
On 11/19/2013 03:32 PM, Akinobu Mita wrote:
The DMA Contiguous Memory Allocator support on x86 is disabled when
swiotlb config option is enabled. So DMA CMA is always disabled on
x86_64 because swiotlb is always enabled. This attempts to support
for DMA CMA with enabling swiotlb config
14 matches
Mail list logo
