https://github.com/rust-bpf/rust-bcc

user-friendly rust bindings for the bpf compiler collection
https://github.com/rust-bpf/rust-bcc

Last synced: 2 months ago
JSON representation

user-friendly rust bindings for the bpf compiler collection

• Host: GitHub
• URL: https://github.com/rust-bpf/rust-bcc
• Owner: rust-bpf
• License: mit
• Created: 2018-02-02T21:59:26.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2023-10-25T20:00:32.000Z (about 1 year ago)
• Last Synced: 2024-10-06T14:10:05.270Z (3 months ago)
• Language: Rust
• Size: 2.97 MB
• Stars: 472
• Watchers: 9
• Forks: 54
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-ccamel - rust-bpf/rust-bcc - user-friendly rust bindings for the bpf compiler collection (Rust)

README

        
# rust-bcc

**Warning! Unmaintained!**

With the advances in other BPF crates in the Rust ecosystem, this crate is no

longer actively maintained. We recommend adopting [libbpf-rs](https://crates.io/crates/libbpf-rs)

## About

Idiomatic Rust bindings for the BPF compiler collection. The goal is to mimic the

Python BCC bindings in https://github.com/iovisor/bcc in a Rusty way.

The C bcc API (as exposed in `bcc-sys`) is very powerful, but it's fairly nontrivial to try to use

it by itself and manage all the resources it allocates safely.

This crate is currently experimental and has several things in it which are either unsafe or not

particularly idiomatic for Rust. Pull requests very much appreciated.

## Prerequisites

* bcc v0.4.0-v0.23.0

## Static linking

This crate allows for statically linking libbpf/libbcc which enables the creation of tools which

have no runtime dependency on matching versions being present on target systems. To statically link,

you may need to compile several dependencies from source. See the `build/ci.sh` script for how those

dependencies are built and how we build and run statically linked examples in CI.

## Getting Started

The best way to learn about how to use this crate right now is to read the examples. The exciting

thing about these examples is that the Rust version isn't really more verbose than the Python

version. In some ways the Rust code is more legible because it's much more natural to work with C

data structure in Rust than it is in Python.

### Building

This library uses features to allow support for multiple versions of bcc. Depending on what version

of bcc you have installed, you may need to use a feature flag while building the examples in-order

to match the expected version of bcc with the version you have installed on your system.

### Examples

* [examples/strlen.rs](https://github.com/rust-bpf/rust-bcc/blob/master/examples/strlen.rs) uses a BPF hashmap to count frequencies of every string that `strlen` is run on. Port of [strlen_count.py](https://github.com/iovisor/bcc/blob/master/examples/tracing/strlen_count.py) to Rust.

* [examples/opensnoop.rs](https://github.com/rust-bpf/rust-bcc/blob/master/examples/opensnoop.rs) uses perf events to track every time a file is opened on the system. Port of [opensnoop.py](https://github.com/iovisor/bcc/blob/master/tools/opensnoop.py) to Rust.

* [examples/softirq.rs](https://github.com/rust-bpf/rust-bcc/blob/master/examples/softirqs.rs) uses

  kernel tracepoints to report time spent in softirq handlers. Port of [softirqs.py](https://github.com/iovisor/bcc/blob/master/tools/softirqs.py) to Rust.