netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v5 bpf-next 0/2] bpf: Add a new API libbpf_num_possible_cpus()
@ 2019-06-08  2:19 Hechao Li
  2019-06-08  2:19 ` [PATCH v5 bpf-next 1/2] bpf: add " Hechao Li
  2019-06-08  2:19 ` [PATCH v5 bpf-next 2/2] bpf: use libbpf_num_possible_cpus Hechao Li
  0 siblings, 2 replies; 3+ messages in thread
From: Hechao Li @ 2019-06-08  2:19 UTC (permalink / raw)
  To: bpf; +Cc: netdev, daniel, ast, kernel-team, Hechao Li

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.

Hechao Li (2):
  bpf: add a new API libbpf_num_possible_cpus()
  bpf: use libbpf_num_possible_cpus in bpftool and selftests

 tools/bpf/bpftool/common.c             | 53 +++---------------------
 tools/lib/bpf/libbpf.c                 | 57 ++++++++++++++++++++++++++
 tools/lib/bpf/libbpf.h                 | 16 ++++++++
 tools/lib/bpf/libbpf.map               |  1 +
 tools/testing/selftests/bpf/bpf_util.h | 37 +++--------------
 5 files changed, 84 insertions(+), 80 deletions(-)

-- 
2.17.1


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-06-08  2:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-08  2:19 [PATCH v5 bpf-next 0/2] bpf: Add a new API libbpf_num_possible_cpus() Hechao Li
2019-06-08  2:19 ` [PATCH v5 bpf-next 1/2] bpf: add " Hechao Li
2019-06-08  2:19 ` [PATCH v5 bpf-next 2/2] bpf: use libbpf_num_possible_cpus Hechao Li

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).