Lines Matching refs:with

33 BSD systems, in order to filter packets in the kernel with tools such as
35 where it evolved into eBPF (_extended_ BPF), a faster version with more
45 although the JIT-compiler does not work with Windows at this time.
85 [crates.io](https://crates.io/crates/rbpf) version (may not be up-to-date with
90 Here are the steps to follow to run an eBPF program with rbpf:
111 This behavior can be replicated with rbpf, but it is not mandatory. For this
121   created to be compatible with the kernel, while saving the effort to manually
143 // called with EbpfVmMbuff:: prefix
146 // called with EbpfVmFixedMbuff:: prefix
151 // called with EbpfVmRaw:: prefix
154 // called with EbpfVmNoData:: prefix
162 checked with a very simple verifier (nothing close to the one for Linux
163 kernel). Users are also able to replace it with a custom verifier.
183 program after the VM instance creation. This program is checked with the
209 useful for programs that should be compatible with the Linux kernel and
253 the JIT-compiled program should be the same as with the interpreter, but it
402     // Load a program from an ELF file, e.g. compiled from C to eBPF with
421     // This is our data: a real packet, starting with Ethernet header
444     // to the sk_buff that eBPF programs use with tc and in Linux kernel.
578 The `assembler` module is available, albeit with reduced debugging features. It
600 of the author's knowledge. The author happens to work with BPF on Linux and to
601 know how uBPF works, and he wanted to learn and experiment with Rust—no more
604 ### What are the differences with uBPF?
619 * The distinct structs permitting to run program either on packet data, or with
627 ### Can I use it with the “classic” BPF (a.k.a cBPF) version?
629 No. This crate only works with extended BPF (eBPF) programs. For cBPF programs,
638 kernel comes with [some additional
648 * The interaction with maps is done through the use of specific helpers, so
650   in the kernel (if on Linux), to communicate with in-kernel eBPF programs for
657 The ”verifier” of this crate is very short and has nothing to do with the
672 could be a good idea to test your program with the interpreter first.
674 Oh, and if your program has infinite loops, even with the interpreter, you're
682   runtime (yet). Use with caution.
693 * Improve safety of JIT-compiled programs with runtime memory checks.
697   with clang?
705 integration with other projects, the rbpf crate is distributed under the terms
720   eBPF virtual machine, with a JIT-compiler and disassembler (and also