Magnus Karlsson

On Tue, Mar 3, 2020 at 6:51 PM Simon Hardy-Francis wrote: > [@magnus-karlsson ] libbpf sets this > flag automatically if you register the same umem more than twice, so...

What kernel are you using and what are the drivers you have tried? Please also post the piece of code that triggers the problem, if it is small enough. Fine...

32-bit support for ARM was not working until this patch made it into the kernel: commit 76f34950779f3d7847c94615232dff2cdc2f9844 Author: Ivan Khoronzhuk Date: Mon Sep 23 15:39:28 2019 -0700 mm: mmap: increase...

If you use 5.3 or older, it works on ARM 64-bit and x86 with a 64-bit kernel for both 32 and 64 bit user space. It only works for 32-bit...

And the previous comment is only valid for AF_XDP. As for XDP, I do not know.

On Sun, Jun 13, 2021 at 10:04 PM Toke Høiland-Jørgensen < ***@***.***> wrote: > Adarsh Sunilkumar ***@***.***> writes: > > > @tohojo any idea why it is happening like that...

The driver provides the NIC with buffer addresses. These are used by the NIC when it gets packets to DMA the packet into. When you have a zero-copy umem, these...

You are likely running a too new libbpf on an older kernel. In 5.4-rcX, there is a new feature that changes the size of the offset struct. An old libbpf...

Actually, this should be fixed in libbpf. Will submit a patch. Thanks for detecting this.

> Magnus Karlsson writes: > You are likely running a too new libbpf on an older kernel. In 5.4-rcX, there is a new feature that changes the size of the...