diff options
| author | 2019-06-11 10:36:03 +0200 | |
|---|---|---|
| committer | 2019-06-11 10:36:04 +0200 | |
| commit | 5e2ac390fbd08b2a462db66cef2663e4db0d5191 (patch) | |
| tree | 2ed8d6d46425887dd31d8c2ff146aee98bd25e55 /net/nsh/nsh.c | |
| parent | selftests/bpf : clean up feature/ when make clean (diff) | |
| parent | bpf: use libbpf_num_possible_cpus internally (diff) | |
| download | wireguard-linux-5e2ac390fbd08b2a462db66cef2663e4db0d5191.tar.xz wireguard-linux-5e2ac390fbd08b2a462db66cef2663e4db0d5191.zip | |
Merge branch 'bpf-libbpf-num-cpus'
Hechao Li says:
====================
Getting number of possible CPUs is commonly used for per-CPU BPF maps
and perf_event_maps. Add a new API libbpf_num_possible_cpus() that
helps user with per-CPU related operations and remove duplicate
implementations in bpftool and selftests.
v2: Save errno before calling pr_warning in case it is changed.
v3: Make sure libbpf_num_possible_cpus never returns 0 so that user only
has to check if ret value < 0.
v4: Fix error code when reading 0 bytes from possible CPU file.
v5: Fix selftests compliation issue.
v6: Split commit to reuse libbpf_num_possible_cpus() into two commits:
One commit to remove bpf_util.h from test BPF C programs.
One commit to reuse libbpf_num_possible_cpus() in bpftools
and bpf_util.h.
====================
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'net/nsh/nsh.c')
0 files changed, 0 insertions, 0 deletions
