Documentation/networking/devmem.rst

11 Device memory TCP (devmem TCP) enables receiving data directly into device
79 Header split, flow steering, & RSS are required features for devmem TCP.
84 Flow steering & RSS are used to ensure that only flows targeting devmem land on
85 an RX queue bound to devmem.
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.
150 devmem data by passing the MSG_SOCK_DEVMEM flag to recvmsg::
155 on devmem data.
210 Applications may receive no SO_DEVMEM_* cmsgs. That indicates non-devmem,
277 devmem TCP, even if the dmabuf is not actually backed by devmem. An example of
278 this is udmabuf, which wraps user memory (non-devmem) in a dmabuf.
283 The user application must use MSG_ZEROCOPY flag when sending devmem TCP. Devmem
284 cannot be copied by the kernel, so the semantics of the devmem TX are similar
387 results in a few quirks for payloads of devmem skbs:
390   not possible with devmem skbs.
394 - TCP Dump and bpf can't access devmem packet payloads.
403 ncdevmem is a devmem TCP netcat. It works very similarly to netcat, but