LWN: Comments on "Aya: writing BPF in Rust"

Aya: writing BPF in Rust

notriddle — Sun, 20 Jun 2021 16:39:23 +0000

It also means you get to use Cargo for everything, instead of having to staple together multiple build systems.

Aya: writing BPF in Rust

mkj — Fri, 18 Jun 2021 03:54:15 +0000

Pure Rust crates mean you can very easily cross compile to any Rust-supported platform without having to find suitable libbpf etc to match. You can just copy a static binary (musl) to a beagleboard or raspberry pi and be done with it.

Aya: writing BPF in Rust

xinitrc — Thu, 17 Jun 2021 23:43:57 +0000

Havn't seen this one.
Hopefully it will be marked as production ready.

Aya: writing BPF in Rust

farnz — Thu, 17 Jun 2021 08:50:26 +0000

Apart from the ixy network driver, you mean?

Aya: writing BPF in Rust

xinitrc — Thu, 17 Jun 2021 05:36:51 +0000

still not a single driver on rust

Aya: writing BPF in Rust

danobi — Tue, 15 Jun 2021 20:11:32 +0000

> Pure Rust buys you a smaller surface area for certain types of bugs. In particular any memory safety bugs, because the compiler insists on seeing for itself why all the code you wrote doesn't have memory safety bugs *unless* you explicitly marked it as unsafe.

Yes, for sure. But I don't think it's a pure win. BPF has a huge surface area and libbpf handles lots of crazy features and edge cases. The tradeoff is that a re-implementation not only has to stay "within spec" (which there currently is none) but also keep up with new developments. And that has its own source of fun bugs.

> Also people really like Rust. I actually found I quite enjoy taking a C program and writing an equivalent Rust program, much more so than when I was learning Go for example.

I do as well :). Disclosure: I wrote most of libbpf-rs (the rust wrappers around libbpf): https://github.com/libbpf/libbpf-rs .

Aya: writing BPF in Rust

tialaramex — Tue, 15 Jun 2021 18:50:21 +0000

Pure Rust buys you a smaller surface area for certain types of bugs. In particular any memory safety bugs, because the compiler insists on seeing for itself why all the code you wrote doesn't have memory safety bugs *unless* you explicitly marked it as unsafe. So logically if you experience a memory safety bug, it's not hiding somewhere in apparently safe high-level stuff but must instead be in the (hopefully far smaller) unsafe part. Which also hopefully means the people who *wrote* that part were more careful when doing so.

That can translate into more courage to try things you otherwise wouldn't dare, and then when inevitably something goes wrong into more chance of figuring out where the actual bug is.

Also people really like Rust. I actually found I quite enjoy taking a C program and writing an equivalent Rust program, much more so than when I was learning Go for example.

Aya: writing BPF in Rust

danobi — Tue, 15 Jun 2021 17:03:58 +0000

A pure rust implementation is nice, but rust doesn't have issues with FFI like go does. I'm curious what the pure rust buys the user in this case. Looking forward to see some examples.