Lines Matching refs:this

21 - decides about the actual backing storage where this allocation happens,
22 - takes care of any migration of scatterlist - for all (shared) users of this
28 - needs a mechanism to get access to the scatterlist that makes up this buffer
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
52    associated with this buffer. All these fields are filled in struct
59    If this succeeds, dma_buf_export allocates a dma_buf structure, and
60    returns a pointer to the same. It also associates an anonymous file with this
82    This API installs an fd for the anonymous file associated with this buffer;
96    After this, the buffer-user needs to attach its device with the buffer, which
110 Until this stage, the buffer-exporter has the option to choose not to actually
111 allocate the backing storage for this buffer, but wait for the first buffer-user
126    "dma_buf->ops->" indirection from the users of this interface.
133    It should return the sg_table containing scatterlist for this buffer, mapped
136    If this is being called for the first time, the exporter can now choose to
137    scan through the list of attachments for this buffer, collate the requirements
158    "dma_buf->ops->" indirection from the users of this interface.
166    map_dma_buf, this API also must be implemented by the exporter.
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
189    This API then reduces the refcount for this buffer.
191    If, as a result of this call, the refcount becomes 0, the 'release' file
192    operation related to this fd is called. It calls the dmabuf->ops->release()
209    - and the backing storage has been allocated for this buffer,
210    another new buffer-user intends to attach itself to this buffer, it might
218     Once all users have finished accessing and have unmapped this buffer, the
326    it needs to announce this to the exporter (to facilitate cache flushing and
347    the need to handle this specially in userspace frameworks for buffer sharing
351    Furthermore Android's ION framework already supports this (and is otherwise
353    handles, too). So it's beneficial to support this in a similar fashion on
371    special resources at fault time. So hopefully this is good enough, since
387    exporter hence does not need to duplicate this check.
408    mentioned here because many people seem to want something like this, but if
409    different exporters handle this differently, buffer sharing can fail in
411    upon this implicit synchronization).
422   cases. Userspace can use this to detect support for discovering the dma-buf
437   The problem with doing this via a separate fcntl() call, versus doing it
438   atomically when the fd is created, is that this is inherently racy in a
443   To avoid this problem, userspace must have a way to request O_CLOEXEC