浏览代码

dma-buf: add initial vmap documentation

Signed-off-by: Dave Airlie <airlied@redhat.com>
Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
Dave Airlie 13 年之前
父节点
当前提交
b25b086d23
共有 1 个文件被更改,包括 11 次插入0 次删除
  1. 11 0
      Documentation/dma-buf-sharing.txt

+ 11 - 0
Documentation/dma-buf-sharing.txt

@@ -293,6 +293,17 @@ Access to a dma_buf from the kernel context involves three steps:
    Note that these calls need to always succeed. The exporter needs to complete
    Note that these calls need to always succeed. The exporter needs to complete
    any preparations that might fail in begin_cpu_access.
    any preparations that might fail in begin_cpu_access.
 
 
+   For some cases the overhead of kmap can be too high, a vmap interface
+   is introduced. This interface should be used very carefully, as vmalloc
+   space is a limited resources on many architectures.
+
+   Interfaces:
+      void *dma_buf_vmap(struct dma_buf *dmabuf)
+      void dma_buf_vunmap(struct dma_buf *dmabuf, void *vaddr)
+
+   The vmap call can fail if there is no vmap support in the exporter, or if it
+   runs out of vmalloc space. Fallback to kmap should be implemented.
+
 3. Finish access
 3. Finish access
 
 
    When the importer is done accessing the range specified in begin_cpu_access,
    When the importer is done accessing the range specified in begin_cpu_access,