Timo Beckers

@kwakubiney Sorry! Was looking at program types, not attach types.. Closing this, thanks for investigating.

Superseded by https://github.com/cilium/ebpf/pull/1557 since you disabled pushes from maintainers on your PR.

@smagnani96 I've pushed up a few changes to https://github.com/cilium/ebpf/pull/1572 today. Note that all 'atomic' methods are gone. It wasn't a great design to begin with and @mejedi suggested mmapping over...

@mejedi That sounds reasonable, thanks for sharing your perspective. The downside is this is kind of a breaking change; rebuilding the same code base with a newer version of b2g...

I've updated https://github.com/cilium/ebpf/pull/1572 to emit a Variable to the Collection for every VariableSpec in the CollectionSpec. Get(), Set() and VariablePointer() will return ErrNotSupported on kernels without BPF_F_MMAPABLE. This ensures LoadAndAssign...

@smagnani96 FYI https://github.com/cilium/ebpf/pull/1572 has been merged, and https://github.com/cilium/ebpf/pull/1607 was opened to keep track of the off-heap Go pointers, though keep in mind this might take a while to be resolved...

@smagnani96 I'm planning to continue with https://github.com/cilium/ebpf/pull/1607, but putting it behind a `CollectionOptions.UnsafeMemory` flag. It will take a while before manual memory cleanup is a thing in the Go runtime,...

Closing this for now, since: - the direct memory access feature will remain experimental (behind a build tag) until the Go runtime supports off-heap finalizers - users need to decide...

> Before going down this route: adding wasm to CI kind of implies that we will start maintaining a wasm "port". I personally don't have the capacity to do that....

Hi @alban, any progress here? Are the Getpagesize() changes still required?