GitXplorerGitXplorer
m

node_bpfcc

public
17 stars
2 forks
2 issues

Commits

List of commits on branch master.
Unverified
3d761daff1e7edbc94d9584dc52a6f34a8244b1f

⚙️ disable tests for now

mmildsunrise committed 4 years ago
Unverified
50ebfb2502e280c9cc6bd1165ec5713cbaea6db0

don't include linux/bpf.h directly

mmildsunrise committed 4 years ago
Unverified
782bfea948e1674ca43375e0e966352899140c15

some other changes to adapt to older API

mmildsunrise committed 4 years ago
Unverified
6df829c2a482e4889da85f8ec35e8214c8eec241

😔 un-expose newer functionality for now

mmildsunrise committed 4 years ago
Unverified
495c29a558a940b37dc149b5bd1cd22a7e9ef92a

📦 release 1.0.1

mmildsunrise committed 4 years ago
Unverified
27e3ffdf09a75c77d62d200f5f5481f46517b00f

use new bpf to get better prebuilds

mmildsunrise committed 4 years ago

README

The README file for this repository.

bpfcc

Node.js frontend (aka bindings) for iovisor's BPF Compiler Collection (BCC).

💡 Examples  •  📚 API reference

Usage

Installing

First you need to install BCC on your system. For modern distros (Ubuntu 20.04+) you can use the repository packages. You don't need to install everything, only the C library & development files; for instance, on Ubuntu the following should be enough:

sudo apt install libbpfcc-dev

Then install this module and bpf, which is required as a peer dependency:

npm install bpfcc bpf

Loading & attaching programs

To use it, first pass your program to load or loadSync to compile it:

const { loadSync } = require('bpfcc')

const bpf = loadSync(`
    #include <uapi/linux/ptrace.h>
    #include <linux/blkdev.h>

    BPF_HISTOGRAM(dist);
    BPF_HISTOGRAM(dist_linear);

    int kprobe__blk_account_io_done(struct pt_regs *ctx, struct request *req) {
        dist.increment(bpf_log2l(req->__data_len / 1024));
        dist_linear.increment(req->__data_len / 1024);
        return 0;
    }
`)

Then you need to load & attach your functions to kernel events using the attach* methods:

bpf.attachKprobe('blk_account_io_done', 'kprobe__blk_account_io_done')

Note: By default, functions starting with prefixes like kprobe__ are automatically detected and attached, so the above isn't necessary in this case.

At a later point, if you no longer need it, you can use bpf.detachAll() to detach and unload everything from the kernel. If you don't, it might get called by the GC at some point, but it's not recommended to rely on this.

Accessing maps

Once tracing has started, we can communicate with our eBPF program by accessing its maps (using the get*Map methods). In our case we have two array maps, with uint32 values:

const dist = bpf.getRawArrayMap('dist')
const distLinear = bpf.getRawArrayMap('dist_linear')

// Retrieve current values & parse them
const ys = [...dist].map(x => x.readUInt32LE(0))
console.log(ys)

getRaw*Map methods provide a raw interface which returns Buffers, so we had to parse the values ourselves. But there are also high-level versions that take a conversion object. For convenience, bpf provides a conversion for uint32, so we can write:

const { u32type } = require('bpf')

const dist = bpf.getArrayMap('dist', u32type)
const distLinear = bpf.getArrayMap('dist_linear', u32type)

console.log( [...dist] )

Refer to the bpf module for details on the interface.

The full source code of this example is in bitehist.ts. Remember you'll probably need root to run.

Troubleshooting

Remember that not all features may be available in the kernel you are running, even if they're present in the API and typings. Trying to use a non-available feature will generally result in an EINVAL error.

A reference of eBPF features and minimum kernel versions required for them can be found here.