Skip to content
BCC - Tools for BPF-based Linux IO analysis, networking, monitoring, and more
Branch: master
Clone or download
4ast Merge pull request #2412 from brendangregg/docs
update tools diagram for 2019
Latest commit 35cb9fd Jun 17, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
SPECS spec: added shebang mangling Jan 16, 2019
cmake include libbpf/src/*.c files in the build system Jan 18, 2019
debian debian changelog for v0.10.0 tag May 29, 2019
docs sync with latest libbpf May 29, 2019
examples Revise python tutorial lesson 16 to make sure tutorial text and code … May 29, 2019
images update tools diagram for 2019 Jun 17, 2019
introspection sync to latest libbpf May 17, 2019
man tools/execsnoop: add -T option Jun 7, 2019
scripts get submodules in cmake and package build Jan 17, 2019
snapcraft snapcraft: remove python path wrapper hack May 16, 2019
src build: Rename kheaders location from proc to sys Jun 12, 2019
tests Add basic USDT support for s390x (#2266) Mar 12, 2019
tools tools/execsnoop: add -T option Jun 7, 2019
.clang-format Add TableStorage class for wrapping bpf map tracking Apr 3, 2017
.dockerignore Add multiple build support styles Jul 7, 2015
.gitignore inject: Add support for alloc_page family of functions (#2114) Jan 7, 2019
.gitmodules add kernel libbpf as a submodule Jan 17, 2019
.travis.yml Unify python executables to use `#!/usr/bin/env python` shebang (#2102) Jan 3, 2019
CMakeLists.txt get submodules in cmake and package build Jan 17, 2019
CODEOWNERS Add /tests/ to CODEOWNERS Aug 23, 2017 notes about tools (#2153) Jan 18, 2019
Dockerfile.debian Fixes for debian and ubuntu docker build Aug 17, 2017
Dockerfile.ubuntu Enable Ubuntu/arm64 deb packaging (#1968) Sep 13, 2018
FAQ.txt Updated the FAQ with the error produced if python[2-3]-bcc isn't inst… Feb 5, 2018 Clarify kernel configuration flags (#2286) Mar 23, 2019
LICENSE.txt Create LICENSE.txt Jun 5, 2015 Link to article on how Circonus uses bcc May 8, 2018 add Quick Start Guide for bcc docker Dec 1, 2016 update tools diagram for 2019 Jun 17, 2019

BCC Logo

BPF Compiler Collection (BCC)

BCC is a toolkit for creating efficient kernel tracing and manipulation programs, and includes several useful tools and examples. It makes use of extended BPF (Berkeley Packet Filters), formally known as eBPF, a new feature that was first added to Linux 3.15. Much of what BCC uses requires Linux 4.1 and above.

eBPF was described by Ingo Molnár as:

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.

BCC makes BPF programs easier to write, with kernel instrumentation in C (and includes a C wrapper around LLVM), and front-ends in Python and lua. It is suited for many tasks, including performance analysis and network traffic control.


This example traces a disk I/O kernel function, and populates an in-kernel power-of-2 histogram of the I/O size. For efficiency, only the histogram summary is returned to user-level.

# ./
Tracing... Hit Ctrl-C to end.
     kbytes          : count     distribution
       0 -> 1        : 3        |                                      |
       2 -> 3        : 0        |                                      |
       4 -> 7        : 211      |**********                            |
       8 -> 15       : 0        |                                      |
      16 -> 31       : 0        |                                      |
      32 -> 63       : 0        |                                      |
      64 -> 127      : 1        |                                      |
     128 -> 255      : 800      |**************************************|

The above output shows a bimodal distribution, where the largest mode of 800 I/O was between 128 and 255 Kbytes in size.

See the source: What this traces, what this stores, and how the data is presented, can be entirely customized. This shows only some of many possible capabilities.


See for installation steps on your platform.


See FAQ.txt for the most common troubleshoot questions.

Reference guide

See docs/ for the reference guide to the bcc and bcc/BPF APIs.


Some of these are single files that contain both C and Python, others have a pair of .c and .py files, and some are directories of files.






BPF Introspection:

Tools that help to introspect BPF programs.

  • introspection/bps.c: List all BPF programs loaded into the kernel. 'ps' for BPF programs. Examples.


BPF guarantees that the programs loaded into the kernel cannot crash, and cannot run forever, but yet BPF is general purpose enough to perform many arbitrary types of computation. Currently, it is possible to write a program in C that will compile into a valid BPF program, yet it is vastly easier to write a C program that will compile into invalid BPF (C is like that). The user won't know until trying to run the program whether it was valid or not.

With a BPF-specific frontend, one should be able to write in a language and receive feedback from the compiler on the validity as it pertains to a BPF backend. This toolkit aims to provide a frontend that can only create valid BPF programs while still harnessing its full flexibility.

Furthermore, current integrations with BPF have a kludgy workflow, sometimes involving compiling directly in a linux kernel source tree. This toolchain aims to minimize the time that a developer spends getting BPF compiled, and instead focus on the applications that can be written and the problems that can be solved with BPF.

The features of this toolkit include:

  • End-to-end BPF workflow in a shared library
    • A modified C language for BPF backends
    • Integration with llvm-bpf backend for JIT
    • Dynamic (un)loading of JITed programs
    • Support for BPF kernel hooks: socket filters, tc classifiers, tc actions, and kprobes
  • Bindings for Python
  • Examples for socket filters, tc classifiers, and kprobes
  • Self-contained tools for tracing a running system

In the future, more bindings besides python will likely be supported. Feel free to add support for the language of your choice and send a pull request!



At Red Hat Summit 2015, BCC was presented as part of a session on BPF. A multi-host vxlan environment is simulated and a BPF program used to monitor one of the physical interfaces. The BPF program keeps statistics on the inner and outer IP addresses traversing the interface, and the userspace component turns those statistics into a graph showing the traffic distribution at multiple granularities. See the code here.



Already pumped up to commit some code? Here are some resources to join the discussions in the IOVisor community and see what you want to work on.

External links

Looking for more information on BCC and how it's being used? You can find links to other BCC content on the web in

You can’t perform that action at this time.