Go to file
Tamir Duberstein bdd8ae2d0b *: avoid `_`
This can silently discard information, so we shouldn't do it.
.cargo ci: Include mips architecture in tests
.github ci: run on all branches
.vim Re-organize into a single workspace
.vscode vscode: exclude public-api fixtures from search
assets readme: Add crabby, sync with aya/README.md
aya *: avoid `_`
aya-build aya-build: add explicit irrefutable pattern
aya-ebpf-macros Replace proc-macro-error with proc-macro2-diagnostics
aya-log *: avoid `_`
aya-log-common Appease clippy
aya-log-ebpf-macros Release aya-log-ebpf-macros v0.1.0
aya-log-parser *: avoid Result::is_{ok,err}
aya-obj *: avoid `_`
aya-tool *: appease clippy
ebpf *: avoid `_`
init Appease clippy
test *: avoid `_`
xtask aya: encode bpf(2) contract
.gitignore xtask: remove assumptions from docs command
.gitmodules xtask: move libbpf submodule
.markdownlint-cli2.yaml chore: Disable markdownlint for generated files
.mergify.yml chore: Fix Mergify configuration
.taplo.toml fix: fix rustdocs-args ordering in taplo to -D warnings
CODE_OF_CONDUCT.md .github: Add markdownlint
CONTRIBUTING.md .github: Add markdownlint
Cargo.toml Correctly specify git dependency
LICENSE-APACHE Add license files
LICENSE-MIT Add license files
README.md Introducing Aya Guru on Gurubase.io ()
clippy.sh Extract integration-common for shared types
netlify.toml toml: add formatter and check in CI
release.toml chore: Fix release.toml
rustfmt.toml rustfmt: group_imports = "StdExternalCrate"

README.md

Aya

Crates.io License Build status Book Gurubase

API Documentation

Unreleased Documentation Documentaiton

Community

Discord Awesome

Join the conversation on Discord to discuss anything related to Aya or discover and contribute to a list of Awesome Aya projects.

Overview

eBPF is a technology that allows running user-supplied programs inside the Linux kernel. For more info see What is eBPF.

Aya is an eBPF library built with a focus on operability and developer experience. It does not rely on libbpf nor bcc - it's built from the ground up purely in Rust, using only the libc crate to execute syscalls. With BTF support and when linked with musl, it offers a true compile once, run everywhere solution, where a single self-contained binary can be deployed on many linux distributions and kernel versions.

Some of the major features provided include:

  • Support for the BPF Type Format (BTF), which is transparently enabled when supported by the target kernel. This allows eBPF programs compiled against one kernel version to run on different kernel versions without the need to recompile.
  • Support for function call relocation and global data maps, which allows eBPF programs to make function calls and use global variables and initializers.
  • Async support with both tokio and async-std.
  • Easy to deploy and fast to build: aya doesn't require a kernel build or compiled headers, and not even a C toolchain; a release build completes in a matter of seconds.

Example

Aya supports a large chunk of the eBPF API. The following example shows how to use a BPF_PROG_TYPE_CGROUP_SKB program with aya:

use std::fs::File;
use aya::Ebpf;
use aya::programs::{CgroupSkb, CgroupSkbAttachType};

// load the BPF code
let mut ebpf = Ebpf::load_file("ebpf.o")?;

// get the `ingress_filter` program compiled into `ebpf.o`.
let ingress: &mut CgroupSkb = ebpf.program_mut("ingress_filter")?.try_into()?;

// load the program into the kernel
ingress.load()?;

// attach the program to the root cgroup. `ingress_filter` will be called for all
// incoming packets.
let cgroup = File::open("/sys/fs/cgroup/unified")?;
ingress.attach(cgroup, CgroupSkbAttachType::Ingress)?;

Contributing

Please see the contributing guide.

License

Aya is distributed under the terms of either the MIT license or the Apache License (version 2.0), at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.