linux.git/Documentation/bpf, branch v4.17.4

bpf: Document sockmap '-target bpf' requirement for PROG_TYPE_SK_MSG

2018-04-23T21:42:21+00:00

BPF_PROG_TYPE_SK_MSG programs use a 'void *' for both data and the
data_end pointers. Additionally, the verifier ensures that every
accesses into the values is a __u64 read. This correctly maps on
to the BPF 64-bit architecture.

However, to ensure that when building on 32bit architectures that
clang uses correct types the '-target bpf' option _must_ be
specified. To make this clear add a note to the Documentation.

Signed-off-by: John Fastabend 
Acked-by: Alexei Starovoitov 
Signed-off-by: Daniel Borkmann

bpf, doc: add description wrt native/bpf clang target and pointer size

2018-03-20T22:47:45+00:00

As this recently came up on netdev [0], lets add it to the BPF devel doc.

  [0] https://www.spinics.net/lists/netdev/msg489612.html

Signed-off-by: Daniel Borkmann 
Signed-off-by: Alexei Starovoitov

bpf: add documentation to compare clang "-target bpf" and default target

2018-02-02T10:14:19+00:00

The added documentation explains how generated codes may differ
between clang bpf target and default target, and when to use
each target.

Signed-off-by: Yonghong Song 
Signed-off-by: Daniel Borkmann

bpf, doc: add faq about bpf development process

2017-12-06T22:32:42+00:00

In the same spirit of netdev FAQ, start a BPF FAQ as a collection
of expectations and/or workflow details in the context of BPF patch
processing.

Signed-off-by: Daniel Borkmann 
Acked-by: Alexei Starovoitov 
Signed-off-by: Alexei Starovoitov

bpf: document answers to common questions about BPF

2017-11-01T12:01:47+00:00

to address common misconceptions about what BPF is and what it's not
add short BPF Q&A that clarifies core BPF design principles and
answers some common questions.

Signed-off-by: Alexei Starovoitov 
Acked-by: Daniel Borkmann 
Acked-by: John Fastabend 
Acked-by: Jakub Kicinski 
Signed-off-by: David S. Miller