Bug 1755347 - Networking eBPF: cls_bpf and act_bpf will be fully supported in RHEL 8.2
Summary: Networking eBPF: cls_bpf and act_bpf will be fully supported in RHEL 8.2
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: doc-Release_Notes-8-en-US
Version: 8.2
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Lucie Vařáková
QA Contact: RHEL DPM
Marc Muehlfeld
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-25 09:59 UTC by Jiri Benc
Modified: 2020-01-24 10:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.eBPF for *tc* is now fully supported The Traffic Control (tc) kernel subsystem and the *tc* tool can attach extended Berkeley Packet Filtering (eBPF) programs as packet classifiers and actions for both ingress and egress queueing disciplines. This enables programmable packet processing inside the kernel network data path. eBPF for *tc*, previously available as a technology preview, is now fully supported in RHEL 8.2.
Clone Of:
Environment:
Last Closed: 2020-01-24 10:54:55 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

Description Jiri Benc 2019-09-25 09:59:44 UTC 
cls_bpf and act_bpf are part of the tc subsystem in the Linux kernel. They allow both cBPF and eBPF programs to be used as a way to classify network packets and execute actions on them.

The eBPF part has been Tech Preview in RHEL 8.0 and 8.1. The RHEL 8.0 release notes state:

------
eBPF for tc available as a Technology Preview

As a Technology Preview, the Traffic Control (tc) kernel subsystem and the tc tool can attach extended Berkeley Packet Filtering (eBPF) programs as packet classifiers and actions for both ingress and egress queueing disciplines. This enables programmable packet processing inside the kernel network data path.

(BZ#1699825) 
------

With RHEL 8.2, this will leave the Tech Preview state and will be fully supported.
Note You need to log in before you can comment on or make changes to this bug.