bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hechao Li <hechaol@fb.com>
To: <bpf@vger.kernel.org>
Cc: <netdev@vger.kernel.org>, <daniel@iogearbox.net>,
	<ast@kernel.org>, <kernel-team@fb.com>,
	Hechao Li <hechaol@fb.com>
Subject: [PATCH v6 bpf-next 0/3] Add a new API libbpf_num_possible_cpus()
Date: Mon, 10 Jun 2019 17:56:49 -0700	[thread overview]
Message-ID: <20190611005652.3827331-1-hechaol@fb.com> (raw)

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.


Hechao Li (3):
  bpf: add a new API libbpf_num_possible_cpus()
  selftests/bpf: remove bpf_util.h from BPF C progs
  bpf: use libbpf_num_possible_cpus internally

 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_endian.h      |  1 +
 tools/testing/selftests/bpf/bpf_util.h        | 37 ++----------
 .../selftests/bpf/progs/sockmap_parse_prog.c  |  1 -
 .../bpf/progs/sockmap_tcp_msg_prog.c          |  2 +-
 .../bpf/progs/sockmap_verdict_prog.c          |  1 -
 .../selftests/bpf/progs/test_sysctl_prog.c    |  5 +-
 10 files changed, 90 insertions(+), 84 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-06-11  0:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11  0:56 Hechao Li [this message]
2019-06-11  0:56 ` [PATCH v6 bpf-next 1/3] bpf: add a new API libbpf_num_possible_cpus() Hechao Li
2019-06-11  0:56 ` [PATCH v6 bpf-next 2/3] selftests/bpf: remove bpf_util.h from BPF C progs Hechao Li
2019-06-11  0:56 ` [PATCH v6 bpf-next 3/3] bpf: use libbpf_num_possible_cpus internally Hechao Li
2019-06-11  8:54 ` [PATCH v6 bpf-next 0/3] Add a new API libbpf_num_possible_cpus() Daniel Borkmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190611005652.3827331-1-hechaol@fb.com \
    --to=hechaol@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).