netdev - Re: [PATCH v3 bpf-next 0/4] Add benchmark runner and few benchmarks

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]

Date:   Wed, 13 May 2020 12:23:33 -0700
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     Andrii Nakryiko <andriin@...com>
Cc:     bpf <bpf@...r.kernel.org>,
        Network Development <netdev@...r.kernel.org>,
        Alexei Starovoitov <ast@...com>,
        Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii.nakryiko@...il.com>,
        Kernel Team <kernel-team@...com>
Subject: Re: [PATCH v3 bpf-next 0/4] Add benchmark runner and few benchmarks

On Tue, May 12, 2020 at 12:47 PM Andrii Nakryiko <andriin@...com> wrote:
>
> Add generic benchmark runner framework which simplifies writing various
> performance benchmarks in a consistent fashion.  This framework will be used
> in follow up patches to test performance of perf buffer and ring buffer as
> well.
>
> Patch #1 extracts parse_num_list to be re-used between test_progs and bench.
>
> Patch #2 adds generic runner implementation and atomic counter benchmarks to
> validate benchmark runner's behavior.
>
> Patch #3 implements test_overhead benchmark as part of bench runner. It also
> add fmod_ret BPF program type to a set of benchmarks.
>
> Patch #4 tests faster alternatives to set_task_comm() approach, tested in
> test_overhead, in search for minimal-overhead way to trigger BPF program
> execution from user-space on demand.
>
> v2->v3:
>   - added --prod-affinity and --cons-affinity (Yonghong);
>   - removed ringbuf-related options leftovers (Yonghong);
>   - added more benchmarking results for test_overhead performance discrepancies;

Applied. Thanks