Mina Almasry writes:
> API takes the dma-buf fd as input, and binds it to the netdevice. The
> user can specify the rx queues to bind the dma-buf to.
>
> Suggested-by: Stanislav Fomichev
> Signed-off-by: Mina Almasry
Reviewed-by: Donald Hunter
Mina Almasry writes:
> Add documentation outlining the usage and details of devmem TCP.
>
> Signed-off-by: Mina Almasry
> Reviewed-by: Bagas Sanjaya
Reviewed-by: Donald Hunter
On Mon, 1 Jul 2024 at 20:05, Mina Almasry wrote:
>
> On Fri, Jun 28, 2024 at 3:10 AM Donald Hunter wrote:
> >
> > Mina Almasry writes:
> > > + -
> > > +name: bind-dmabuf
> > > +attributes:
> > > + -
> > > +n
Mina Almasry writes:
> +
> +The user must bind a dmabuf to any number of RX queues on a given NIC using
> +the netlink API::
> +
> + /* Bind dmabuf to NIC RX queue 15 */
> + struct netdev_queue *queues;
> + queues = malloc(sizeof(*queues) * 1);
> +
> + queues[0]._present.type = 1;
Mina Almasry writes:
> + -
> +name: bind-dmabuf
> +attributes:
> + -
> +name: ifindex
> +doc: netdev ifindex to bind the dma-buf to.
Minor nit:
The series uses a mix of dmabuf and dma-buf but the doc additions
(devmem.rst) consistently uses dmabuf. I think it would
Akira Yokosawa writes:
>
> That message of mine just pointed out that the Sphinx bug of false
> duplicate C declaration warning first reported by Mauro (+CC'd) at:
> https://github.com/sphinx-doc/sphinx/issues/8241 --
> "C domain issues when building the Linux Kernel documentation".
> It had not b
