LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

bpf.2: Minor fixes 

Reported-by: Daniel Borkmann <daniel@iogearbox.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2015-06-04 12:48:35 +02:00
parent 842ee0100d
commit 896388c88a
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
man2/bpf.2
View File

@ -70,9 +70,9 @@ Each BPF program is a set of instructions that is safe to run until
its completion.
The in-kernel BPF verifier statically determines that the program
terminates and is safe to execute.
.\" FIXME In the following sentence, what does "takes hold" mean?
During verification, the program takes hold of maps that it intends to use,
so selected maps cannot be removed until the program is unloaded.
During verification, the kernel increments reference counts for each of
the maps that the eBPF program uses,
so that the selected maps cannot be removed until the program is unloaded.
BPF programs can be attached to different events.
.\" FIXME: In the next sentence , "packets" are not "events". What
@ -81,7 +81,8 @@ These events can be packets, tracing
events, and other types that may be added in the future.
A new event triggers execution of the BPF program, which
may store information about the event in the maps.
Beyond storing data, BPF programs may call into in-kernel helper functions.
Beyond storing data, BPF programs may call a fixed set of
in-kernel helper functions.
The same program can be attached to multiple events and different programs can
access the same map:
.\" FIXME Can maps be shared between processes? (E.g., what happens