libbpf_rs/
lib.rs

1//! # libbpf-rs
2//!
3//! `libbpf-rs` is a safe, idiomatic, and opinionated wrapper around
4//! [libbpf](https://github.com/libbpf/libbpf/).
5//!
6//! libbpf-rs, together with `libbpf-cargo` (libbpf cargo plugin) allow you
7//! to write Compile-Once-Run-Everywhere (CO-RE) eBPF programs. Note this document
8//! uses "eBPF" and "BPF" interchangeably.
9//!
10//! More information about CO-RE is [available
11//! here](https://facebookmicrosites.github.io/bpf/blog/2020/02/19/bpf-portability-and-co-re.html).
12//!
13//! ## High level workflow
14//!
15//! 1. Create new rust project (via `cargo new` or similar) at path `$PROJ_PATH`
16//! 2. Create directory `$PROJ_PATH/src/bpf`
17//! 3. Write CO-RE bpf code in `$PROJ_PATH/src/bpf/${MYFILE}.bpf.c`, where `$MYFILE` may be any
18//!    valid filename. Note the `.bpf.c` extension is required.
19//! 4. Create a [build script](https://doc.rust-lang.org/cargo/reference/build-scripts.html) that
20//!    builds and generates a skeleton module using `libbpf_cargo::SkeletonBuilder`
21//! 5. Write your userspace code by importing and using the generated module. Import the
22//!    module by using the [path
23//!    attribute](https://doc.rust-lang.org/reference/items/modules.html#the-path-attribute).
24//!    Your userspace code goes in `$PROJ_PATH/src/` as it would in a normal rust project.
25//! 6. Continue regular rust workflow (ie `cargo build`, `cargo run`, etc)
26//!
27//! ## Alternate workflow
28//!
29//! While using the skeleton is recommended, it is also possible to directly use libbpf-rs.
30//!
31//! 1. Follow steps 1-3 of "High level workflow"
32//! 2. Generate a BPF object file. Options include manually invoking `clang`, creating a build
33//!    script to invoke `clang`, or using `libbpf-cargo` cargo plugins.
34//! 3. Write your userspace code in `$PROJ_PATH/src/` as you would a normal rust project and point
35//!    libbpf-rs at your BPF object file
36//! 4. Continue regular rust workflow (ie `cargo build`, `cargo run`, etc)
37//!
38//! ## Design
39//!
40//! libbpf-rs models various "phases":
41//! ```text
42//!                from_*()        load()
43//!                  |               |
44//!                  v               v
45//!    ObjectBuilder ->  OpenObject  -> Object
46//!                          ^            ^
47//!                          |            |
48//!              <pre-load modifications> |
49//!                                       |
50//!                            <post-load interactions>
51//! ```
52//!
53//! The entry point into libbpf-rs is [`ObjectBuilder`]. `ObjectBuilder` helps open the BPF object
54//! file. After the object file is opened, you are returned an [`OpenObject`] where you can
55//! perform all your pre-load operations. Pre-load means before any BPF maps are created or BPF
56//! programs are loaded and verified by the kernel. Finally, after the BPF object is loaded, you
57//! are returned an [`Object`] instance where you can read/write to BPF maps, attach BPF programs
58//! to hooks, etc.
59//!
60//! You _must_ keep the [`Object`] alive the entire duration you interact with anything inside the
61//! BPF object it represents. This is further documented in [`Object`] documentation.
62//!
63//! ## Example
64//!
65//! This is probably the best way to understand how libbpf-rs and libbpf-cargo work together.
66//!
67//! [See example here](https://github.com/libbpf/libbpf-rs/tree/master/examples/runqslower).
68
69pub mod btf;
70mod error;
71mod iter;
72mod link;
73mod linker;
74mod map;
75mod netfilter;
76mod object;
77mod perf_buffer;
78mod print;
79mod program;
80pub mod query;
81mod ringbuf;
82mod skeleton;
83mod streams;
84mod tc;
85mod tracepoint;
86mod user_ringbuf;
87mod util;
88mod xdp;
89
90pub use libbpf_sys;
91
92pub use crate::btf::Btf;
93pub use crate::btf::HasSize;
94pub use crate::btf::ReferencesType;
95pub use crate::error::Error;
96pub use crate::error::ErrorExt;
97pub use crate::error::ErrorKind;
98pub use crate::error::Result;
99pub use crate::iter::Iter;
100pub use crate::link::Link;
101pub use crate::linker::Linker;
102pub use crate::map::BatchedMapIter;
103pub use crate::map::Map;
104pub use crate::map::MapCore;
105pub use crate::map::MapFdInfo;
106pub use crate::map::MapFlags;
107pub use crate::map::MapHandle;
108pub use crate::map::MapImpl;
109pub use crate::map::MapInfo;
110pub use crate::map::MapKeyIter;
111pub use crate::map::MapMut;
112pub use crate::map::MapType;
113pub use crate::map::OpenMap;
114pub use crate::map::OpenMapImpl;
115pub use crate::map::OpenMapMut;
116pub use crate::netfilter::NetfilterOpts;
117pub use crate::netfilter::NFPROTO_IPV4;
118pub use crate::netfilter::NFPROTO_IPV6;
119pub use crate::netfilter::NF_INET_FORWARD;
120pub use crate::netfilter::NF_INET_LOCAL_IN;
121pub use crate::netfilter::NF_INET_LOCAL_OUT;
122pub use crate::netfilter::NF_INET_POST_ROUTING;
123pub use crate::netfilter::NF_INET_PRE_ROUTING;
124pub use crate::object::AsRawLibbpf;
125pub use crate::object::MapIter;
126pub use crate::object::Object;
127pub use crate::object::ObjectBuilder;
128pub use crate::object::OpenObject;
129pub use crate::object::ProgIter;
130pub use crate::perf_buffer::PerfBuffer;
131pub use crate::perf_buffer::PerfBufferBuilder;
132pub use crate::print::get_print;
133pub use crate::print::set_print;
134pub use crate::print::PrintCallback;
135pub use crate::print::PrintLevel;
136pub use crate::program::CgroupIterOpts;
137pub use crate::program::CgroupIterOrder;
138pub use crate::program::Input as ProgramInput;
139pub use crate::program::IterOpts;
140pub use crate::program::KprobeMultiOpts;
141pub use crate::program::KprobeOpts;
142pub use crate::program::MapIterOpts;
143pub use crate::program::OpenProgram;
144pub use crate::program::OpenProgramImpl;
145pub use crate::program::OpenProgramMut;
146pub use crate::program::Output as ProgramOutput;
147pub use crate::program::PerfEventOpts;
148pub use crate::program::Program;
149pub use crate::program::ProgramAttachType;
150pub use crate::program::ProgramImpl;
151pub use crate::program::ProgramMut;
152pub use crate::program::ProgramType;
153pub use crate::program::UprobeMultiOpts;
154pub use crate::program::UprobeOpts;
155pub use crate::program::UsdtOpts;
156pub use crate::ringbuf::RingBuffer;
157pub use crate::ringbuf::RingBufferBuilder;
158pub use crate::tc::TcAttachPoint;
159pub use crate::tc::TcHook;
160pub use crate::tc::TcHookBuilder;
161pub use crate::tc::TC_CUSTOM;
162pub use crate::tc::TC_EGRESS;
163pub use crate::tc::TC_H_CLSACT;
164pub use crate::tc::TC_H_INGRESS;
165pub use crate::tc::TC_H_MIN_EGRESS;
166pub use crate::tc::TC_H_MIN_INGRESS;
167pub use crate::tc::TC_INGRESS;
168pub use crate::tracepoint::RawTracepointOpts;
169pub use crate::tracepoint::TracepointCategory;
170pub use crate::tracepoint::TracepointOpts;
171pub use crate::user_ringbuf::UserRingBuffer;
172pub use crate::user_ringbuf::UserRingBufferSample;
173pub use crate::util::num_possible_cpus;
174pub use crate::xdp::Xdp;
175pub use crate::xdp::XdpFlags;
176
177/// An unconstructible dummy type used for tagging mutable type
178/// variants.
179#[doc(hidden)]
180#[derive(Copy, Clone, Debug)]
181pub enum Mut {}
182
183
184/// Used for skeleton -- an end user may not consider this API stable
185#[doc(hidden)]
186pub mod __internal_skel {
187    pub use super::skeleton::*;
188}
189
190/// Skeleton related definitions.
191pub mod skel {
192    pub use super::skeleton::OpenSkel;
193    pub use super::skeleton::Skel;
194    pub use super::skeleton::SkelBuilder;
195}
libbpf_rs/lib.rs

libbpf_rs/
lib.rs
