Re: [RFC 3/3] mm: iommu: The Virtual Contiguous Memory Manager

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Zach Pfeffer
Date: Monday, July 12, 2010 - 10:21 pm

Joerg Roedel wrote:

The grist to the DMA-API mill is the opaque scatterlist. Each
scatterlist element brings together a physical address and a bus
address that may be different. The set of scatterlist elements
constitute both the set of physical buffers and the mappings to those
buffers. My approach separates these two things into a struct physmem
which contains the set of physical buffers and a struct reservation
which contains the set of bus addresses (or device addresses). Each
element in the struct physmem may be of various lengths (without
resorting to chaining). A map call maps the one set to the other. 

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFC 2/3] mm: iommu: A physical allocator for the VCMM, Zach Pfeffer, (Tue Jun 29, 10:55 pm)
Re: [RFC 3/3] mm: iommu: The Virtual Contiguous Memory Manager, Zach Pfeffer, (Mon Jul 12, 10:21 pm)
Re: [RFC 3/3] mm: iommu: The Virtual Contiguous Memory Manager, Russell King - ARM Linux, (Tue Jul 13, 2:02 am)
Re: [RFC 3/3] mm: iommu: The Virtual Contiguous Memory Manager, Russell King - ARM Linux, (Thu Jul 22, 12:51 am)