From 3dc0ed02a2c774ceaf09ba7a6a3a54f43fe5d885 Mon Sep 17 00:00:00 2001 From: Ivan Babrou Date: Tue, 27 Feb 2024 19:25:08 -0800 Subject: [PATCH] Modernize ebpf description --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 199b8965..a7863db1 100644 --- a/README.md +++ b/README.md @@ -13,12 +13,12 @@ Prometheus exporter for custom eBPF metrics and OpenTelemetry traces. Motivation of this exporter is to allow you to write eBPF code and export metrics that are not otherwise accessible from the Linux kernel. -eBPF was [described by](https://lkml.org/lkml/2015/4/14/232) Ingo Molnár as: +[ebpf.io](https://ebpf.io/what-is-ebpf/) describes eBPF: -> One of the more interesting features in this cycle is the ability to attach -> eBPF programs (user-defined, sandboxed bytecode executed by the kernel) -> to kprobes. This allows user-defined instrumentation on a live kernel image -> that can never crash, hang or interfere with the kernel negatively. +> eBPF 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 to change kernel source code or load kernel modules. An easy way of thinking about this exporter is bcc tools as prometheus metrics: