Yes! At the XDP summit we were discussing pipe-lining XDP programs in general, with different stages of the pipeline potentially using specific hardware capabilities or even being directly mappable on

+1 I was thinking about using eBPF to direct to NIC queues but concluded that doing a redirect to a VF is cleaner. Especially if the PF driver supports VF representatives we could potentially just use

I think of SR-IOV VFs a way of grouping queues. If HW is capable of directing to a queue it's usually capable of directing to a VF as well. And the VF could have all other traffic disabled so you woul

To do BPF RSS we need a way to select the queue which I think is all Jasper wanted. So we will have to tackle the queue selection at some point. The main obstacle with it for me is to define what queu

Yes, although if we expect XDP to be target of offloading efforts putting the demux here doesn't seem like an entirely bad idea. We could say demux is just an API that more capable drivers/HW can impl

Acked-by: Jakub Kicinski <jakub.kicinski@...> Sorry about the delay.

Thinking about next steps - do we expect the 32b operations to clear the upper halves of the registers? The interpreter does it, and so does x86. I don't think we can load 32bit-only programs on 64bit

Hm. Perhaps it's a blunder on my side, but let's take: r1 = ~0ULL w1 = 0 # use r1 on x86 and the interpreter, the w1 = 0 will clear upper 32bits, so r1 ends up as 0. 32b arches may translate this to s

I think Daniel meant for nfp offload. The offload restrictions are quite involved, are we going to be able to express those? This is a bit simpler but reminds me of the TC flower capability discussion

To my understanding it's useful in two ways: - some less fortunate distros (Debian) reportedly need a kernel build to package bpftool, and for libbpf the same would have to happen. At least that's wha

Do you pin the tail call map? If tail call map is not kept open or pinned it will get flushed by the kernel (latest bpftool will print a warning about it). sockex3 keeps the fd open, that's why it wor

Try: bpftool map pin id $YOUR_ID /sys/fs/bpf/my_map and see if the prog array updates stick after that.

Unfortunately current SR-IOV implementation on the CX and LX series of cards does not provide enough resources on the VFs to implement XDP in driver mode :(