Lines Matching refs:it

9 buffer sharing API, how to use it for exporting and using shared buffers.
29    in memory, mapped into its own address space, so it can access the same area
37 1. Exporter announces that it wishes to export a buffer
39    passes it around to potential buffer-users based on use case
43 6. when buffer-user is done using this buffer completely, it 'disconnects'
49    The buffer exporter announces its wish to export a buffer. In this, it
61    buffer, so it can be exported. On failure to allocate the dma_buf object,
62    it returns NULL.
70    zeroes it out and pre-populates exp_name in it.
88    it.
94    it.
117    Whenever a buffer-user wants to use the buffer for any DMA, it asks for
141    Based on enum dma_data_direction, it might be possible to have multiple users
145    map_dma_buf() operation can return -EINTR if it is interrupted by a signal.
150    Once the DMA for the current buffer-user is over, it signals 'end-of-DMA' to
169 6. when buffer-user is done using this buffer, it 'disconnects' itself from the
172    After the buffer-user has no more interest in using this buffer, it should
175    - it first detaches itself from the buffer.
210    another new buffer-user intends to attach itself to this buffer, it might
213    In case it is allowed by the exporter:
229    map_dma_buf() API has been called, it simply returns an error.
237   kernel needs to shuffle the data around first before sending it away.
255    context, it needs to notify the exporter of the access that is about to
278    PAGE_SIZE size. Before accessing a chunk it needs to be mapped, which returns
316    The vmap call can fail if there is no vmap support in the exporter, or if it
320    unmaps it once. Protection against concurrent vmap/vunmap calls is provided
326    it needs to announce this to the exporter (to facilitate cache flushing and
345    In many processing pipelines it is sometimes required that the cpu can access
348    it's ideal if the dma_buf fd itself can be used to access the backing storage
353    handles, too). So it's beneficial to support this in a similar fashion on
360    Similar to the motivation for kernel cpu access it is again important that
391    possible, it needs to fake coherency by manually shooting down ptes when
394    the dma_buf file stored in vma->vm_file with it's own if pte shootdown is
434   access to buffers, via the leaked fd, to which it should otherwise
437   The problem with doing this via a separate fcntl() call, versus doing it
439   multi-threaded app[3].  The issue is made worse when it is library code
449   coherency for mmap support, it needs to be able to zap all the ptes pointing