Lines Matching refs:dmabuf

12 memory (dmabuf). The feature is currently implemented for TCP sockets.
102 The user must bind a dmabuf to any number of RX queues on a given NIC using
105 	/* Bind dmabuf to NIC RX queue 15 */
126 The netlink API returns a dmabuf_id: a unique ID that refers to this dmabuf
129 The user can unbind the dmabuf from the netdevice by closing the netlink socket
133 Note that any reasonably well-behaved dmabuf from any exporter should work with
134 devmem TCP, even if the dmabuf is not actually backed by devmem. An example of
135 this is udmabuf, which wraps user memory (non-devmem) in a dmabuf.
141 The socket must be flow steered to the dmabuf bound RX queue::
157 Devmem data is received directly into the dmabuf bound to the NIC in 'NIC
169 				/* Frag landed in dmabuf.
171 				 * dmabuf_cmsg->dmabuf_id is the dmabuf the
175 				 * the dmabuf where the frag starts.
202 - SCM_DEVMEM_DMABUF: this indicates the fragment landed in the dmabuf indicated
211 regular TCP data that landed on an RX queue not bound to a dmabuf.
225 Failure to do so will exhaust the limited dmabuf that is bound to the RX queue