Every boring problem found in eBPF (2022)(tmpout.sh)

Every boring problem found in eBPF (2022)

https://tmpout.sh/2/4.html

14 comments

BPF recently got published as an RFC[1], posted here[2] today and earlier here[3][4].

[1]: https://datatracker.ietf.org/doc/html/rfc9669

[2]: https://news.ycombinator.com/item?id=42051950

[3]: https://news.ycombinator.com/item?id=42024377

[4]: https://news.ycombinator.com/item?id=42038371

tptacek2년 전

This is so weird to me. It's not an interoperable standard. It isn't even interoperable on Linux, the one OS where it's popular.

maxmcd2년 전

There is an explanation here: https://lwn.net/ml/all/20241105035101.GD41004@maniforge/

tptacek2년 전

Right, for offload, but XDP programs also depend on helper definitions, which themselves have not been consistent between versions of the Linux kernel.

stefan_2년 전

And some (most?) of the helpers end up being "read memory at X", which has some obvious problems with offloading.

tptacek2년 전

I mean, there really is working XDP offload (Netronome, right?) so it can be made to work, but this spec doesn't define the hardest part of interoperability.

_flux2년 전

It probably still helps to have a standardised baseline. Then the vendors can just document deviations from it, and the deviations are probably quite small, not necessating new compilers for example (just guessing here ;)).

kimixa2년 전

If you wanted it to become an interoperable standard, that's the obvious step, right?

[deleted]2년 전

Retr0id2년 전

By the way, this article is published as part of the tmp.0ut zine, and the CFP for the next issue is currently open: https://tmpout.sh/blog/vol4-cfp.html

remram2년 전

I'm usually against separate "mobile versions" of websites but wow, this needs one.

humanfromearth92년 전

Wow that's a tl;dr for me. Not only because of the length, also because of format. Not very readable on a smartphone...

[deleted]2년 전

warambo10102년 전