mirror of https://github.com/mkerrisk/man-pages
bpf.2: Minor tweaks
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
4fba111eca
commit
dc079fa280
14
man2/bpf.2
14
man2/bpf.2
|
@ -68,7 +68,7 @@ A user process can create multiple maps (with key/value-pairs being
|
||||||
opaque bytes of data) and access them via file descriptors.
|
opaque bytes of data) and access them via file descriptors.
|
||||||
eBPF programs can access maps from inside the kernel in parallel.
|
eBPF programs can access maps from inside the kernel in parallel.
|
||||||
.\"
|
.\"
|
||||||
.\" FIXME What does the previous sentence mean?
|
.\" FIXME!! What does the previous sentence mean?
|
||||||
.\"
|
.\"
|
||||||
.\" Isn't "from inside the kernel" redundant? (I mean: all eBPF programs
|
.\" Isn't "from inside the kernel" redundant? (I mean: all eBPF programs
|
||||||
.\" are running inside the kernel, right?)
|
.\" are running inside the kernel, right?)
|
||||||
|
@ -273,7 +273,7 @@ and attributes as specified in
|
||||||
.IR value_size ,
|
.IR value_size ,
|
||||||
and
|
and
|
||||||
.IR max_entries .
|
.IR max_entries .
|
||||||
.\" FIXME: In the next sentence, what does "process-local" mean?
|
.\" FIXME!! In the next sentence, what does "process-local" mean?
|
||||||
On success, this operation returns a process-local file descriptor.
|
On success, this operation returns a process-local file descriptor.
|
||||||
On error, \-1 is returned and
|
On error, \-1 is returned and
|
||||||
.I errno
|
.I errno
|
||||||
|
@ -315,7 +315,7 @@ expects to read 8 bytes from
|
||||||
.I key
|
.I key
|
||||||
pointer, but
|
pointer, but
|
||||||
.IR "fp\ -\ 4"
|
.IR "fp\ -\ 4"
|
||||||
.\" FIXME I'm lost! What is 'fp' in this context?
|
.\" FIXME!! I'm lost! What is 'fp' in this context?
|
||||||
starting address will cause out-of-bounds stack access.
|
starting address will cause out-of-bounds stack access.
|
||||||
|
|
||||||
Similarly, when a map is created with a
|
Similarly, when a map is created with a
|
||||||
|
@ -562,7 +562,7 @@ The following map types are supported:
|
||||||
.TP
|
.TP
|
||||||
.B BPF_MAP_TYPE_HASH
|
.B BPF_MAP_TYPE_HASH
|
||||||
.\" commit 0f8e4bd8a1fc8c4185f1630061d0a1f2d197a475
|
.\" commit 0f8e4bd8a1fc8c4185f1630061d0a1f2d197a475
|
||||||
.\" FIXME Please review the following list of points, which draws
|
.\" FIXME!! Please review the following list of points, which draws
|
||||||
.\" heavily from the commit message, but reworks the text significantly
|
.\" heavily from the commit message, but reworks the text significantly
|
||||||
.\" and so may have introduced errors.
|
.\" and so may have introduced errors.
|
||||||
Hash-table maps have the following characteristics:
|
Hash-table maps have the following characteristics:
|
||||||
|
@ -590,7 +590,7 @@ optimized for speed of lookup.
|
||||||
.TP
|
.TP
|
||||||
.B BPF_MAP_TYPE_ARRAY
|
.B BPF_MAP_TYPE_ARRAY
|
||||||
.\" commit 28fbcfa08d8ed7c5a50d41a0433aad222835e8e3
|
.\" commit 28fbcfa08d8ed7c5a50d41a0433aad222835e8e3
|
||||||
.\" FIXME Please review the following list of points, which draws
|
.\" FIXME!! Please review the following list of points, which draws
|
||||||
.\" heavily from the commit message, but reworks the text significantly
|
.\" heavily from the commit message, but reworks the text significantly
|
||||||
.\" and so may have introduced errors.
|
.\" and so may have introduced errors.
|
||||||
Array maps have the following characteristics:
|
Array maps have the following characteristics:
|
||||||
|
@ -854,7 +854,6 @@ ioctl(event_fd, PERF_EVENT_IOC_SET_BPF, prog_fd);
|
||||||
.\"
|
.\"
|
||||||
.\"
|
.\"
|
||||||
.SH EXAMPLES
|
.SH EXAMPLES
|
||||||
.\" FIXME It would be nice if this was a complete working example
|
|
||||||
.nf
|
.nf
|
||||||
/* bpf+sockets example:
|
/* bpf+sockets example:
|
||||||
* 1. create array map of 256 elements
|
* 1. create array map of 256 elements
|
||||||
|
@ -1038,7 +1037,7 @@ commands require the caller to have the
|
||||||
.B CAP_SYS_ADMIN
|
.B CAP_SYS_ADMIN
|
||||||
capability.
|
capability.
|
||||||
|
|
||||||
.\" FIXME Alexei, is the following correct?
|
.\" FIXME!! Alexei, is the following correct?
|
||||||
eBPF objects (maps and programs) can be shared between processes.
|
eBPF objects (maps and programs) can be shared between processes.
|
||||||
For example, after
|
For example, after
|
||||||
.BR fork (2),
|
.BR fork (2),
|
||||||
|
@ -1062,7 +1061,6 @@ and passing structures as function arguments.)
|
||||||
Some examples can be found in the
|
Some examples can be found in the
|
||||||
.I samples/bpf/*_kern.c
|
.I samples/bpf/*_kern.c
|
||||||
files in the kernel source tree.
|
files in the kernel source tree.
|
||||||
.\" samples/bpf/*_kern.c + samples/bpf/Makefile ?
|
|
||||||
.\" There are also examples for the tc classifier, in the iproute2
|
.\" There are also examples for the tc classifier, in the iproute2
|
||||||
.\" project, in examples/bpf
|
.\" project, in examples/bpf
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
|
|
Loading…
Reference in New Issue