Skip to content

Avoid serializing ELFs to the filesystem as part of BPF load

Closed

Description

Currently, the compilation process for eBPF programs for endpoints is to first invoke the compiler to create an ELF representing the datapath code onto the filesystem, then use pkg/elf to create a templated copy with the individual endpoint's data inside, then load this ELF into the kernel.

Now that we are moving more and more code over to cilium/ebpf for loading the datapath, we could avoid creating the ELFs on the filesystem altogether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    kind/cleanupThis includes no functional changes.This includes no functional changes.pinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.sig/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.sig/loaderImpacts the loading of BPF programs into the kernel.Impacts the loading of BPF programs into the kernel.staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions