netdev - Re: [PATCH v4 bpf-next 0/2] bpf: Add a new API libbpf_num_possible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1ba65555-b7a5-3c8d-b5c8-3432dbb2770b@iogearbox.net>
Date:   Fri, 7 Jun 2019 23:26:33 +0200
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Hechao Li <hechaol@...com>, bpf@...r.kernel.org
Cc:     netdev@...r.kernel.org, ast@...nel.org, kernel-team@...com
Subject: Re: [PATCH v4 bpf-next 0/2] bpf: Add a new API
 libbpf_num_possible_cpus()

On 06/07/2019 06:37 PM, Hechao Li wrote:
> 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.
> 
> v4: Fixed error code when reading 0 bytes from possible CPU file
> 
> 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(-)

Series applied, thanks!

P.s.: Please retain full history (v1->v2->v3->v4) in cover letter next time as
that is typical convention and helps readers of git log to follow what has been
changed over time.