Skip to main content

BPF/eBPF
bofreq-thaler-bpf-ebpf-00

The information below is for an older version of this BOF request.
Document Type Proposed BOF request Snapshot
Title BPF/eBPF
Last updated 2023-01-07
State Proposed
Editors Dave Thaler , Christoph Hellwig
Responsible leadership
Send notices to (None)
bofreq-thaler-bpf-ebpf-00

Name: BPF/eBPF

Description

eBPF (which is no longer an acronym for anything), also commonly referred to as BPF, is a revolutionary technology with origins in the Linux kernel that can run sandboxed programs in a privileged context such as the operating system kernel. It is used to safely and efficiently extend the capabilities of the kernel without requiring changing kernel source code or load kernel modules.

(e)BPF is increasing being used beyond just the Linux kernel, with implementations in network interface cards, Windows, etc. As such, this effort aims to document and standardize existing (e)BPF use. The IETF should also define processes for future extensions since (e)BPF has constantly been added to over time.

Required Details

  • Status: WG Forming?
  • Responsible AD: Erik Kline
  • BOF proponents: Dave Thaler <dthaler@microsoft.com>, Christoph Hellwig <hch@infradead.org>
  • BOF chairs: TBD
  • Number of people expected to attend: 40
  • Length of session (1 or 2 hours): 2 hours
  • Conflicts (whole Areas and/or WGs)
  • Chair Conflicts: TBD
  • Technology Overlap: spring, intarea
  • Key Participant Conflict: teep, suit, rats, nfsv4

Information for IAB/IESG

The proposed work is to document existing practice, not define new protocols or mechanisms per se.

Agenda

  • Problem statement
  • Proposed scope of work
  • Instruction Set Architecture
  • (Time permitting) ELF file format
  • Next steps