On Tue, Mar 15, 2011 at 06:34:42PM +0900, daeinki wrote: > Russell King - ARM Linux ì ê: >> On Tue, Mar 15, 2011 at 10:45:50AM +0900, InKi Dae wrote: >>> 2011/3/14 Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>: >>>> On Mon, Mar 14, 2011 at 09:37:51PM +0900, KyongHo Cho wrote: >>>>> I have also noticed that dma_map_single/page/sg() can map physical >>>>> memory into an arbitrary device address region. >>>>> But it is not enough solution for various kinds of IOMMUs. >>>>> As Kukjin Kim addressed, we need to support larger page size than 4KB >>>>> because we can reduce TLB miss when we have larger page size. >>>>> >>>>> Our IOMMU(system mmu) supports all page size of ARM architecture >>>>> including 16MB, 1MB, 64KB and 4KB. >>>>> Since the largest size supported by buddy system of 32-bit architecture is 4MB, >>>>> our system support all page sizes except 16MB. >>>>> We proved that larger page size is helpful for DMA performance >>>>> significantly (more than 10%, approximately). >>>>> Big page size is not a problem for peripheral devices >>>>> because their address space is not suffer from external fragmentation. >>>> 1. dma_map_single() et.al. is used for mapping *system* *RAM* for devices >>>> using whatever is necessary. It must not be used for trying to setup >>>> arbitary other mappings. >>>> >>>> 2. It doesn't matter where the memory for dma_map_single() et.al. comes >>>> from provided the virtual address is a valid system RAM address or >>>> the struct page * is a valid struct page in the memory map (iow, you >>>> can't create this yourself.) >>> You mean that we cannot have arbitrary virtual address mapping for >>> iommu based device? >> >> No. I mean exactly what I said - I'm talking about the DMA API in the >> above two points. The implication is that you can not create arbitary >> mappings of non-system RAM with the DMA API. >> > sorry but I couldn't understand exactly what you said. could you give me > your answer one more time? > does non-system RAM mean reserved memory regions? if not, is it > arbitrary virtual address space that isn't kernel or user virtual > address space and is the space for iommu based deivce? For dma_map_single(dev, addr, size, dir), basically: for (a = addr; a < addr + size; a += PAGE_SIZE) BUG_ON(!virt_addr_valid(a)); For dma_map_page(dev, page, offset, size, dir), 'page' must be something obtained from one of the page-based kernel allocators (so either refering to a page in the *existing* lowmem or highmem memory) _and_ you must not use offset/size to then point at something outside that. So, if you take something out of the kernel's knowledge of what is memory, you can't then use the DMA API with it. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
