All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Andrii Nakryiko <andriin@fb.com>
Cc: bpf <bpf@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Alexei Starovoitov <ast@fb.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH v3 bpf-next 0/4] Add benchmark runner and few benchmarks
Date: Wed, 13 May 2020 12:23:33 -0700	[thread overview]
Message-ID: <CAADnVQ+VdbzyRh0vUAZb4CaAUa9yncwSudswXozD+eS17yRT4Q@mail.gmail.com> (raw)
In-Reply-To: <20200512192445.2351848-1-andriin@fb.com>

On Tue, May 12, 2020 at 12:47 PM Andrii Nakryiko <andriin@fb.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

      parent reply	other threads:[~2020-05-13 19:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 19:24 [PATCH v3 bpf-next 0/4] Add benchmark runner and few benchmarks Andrii Nakryiko
2020-05-12 19:24 ` [PATCH v3 bpf-next 1/4] selftests/bpf: extract parse_num_list into generic testing_helpers.c Andrii Nakryiko
2020-05-13  1:08   ` Yonghong Song
2020-05-12 19:24 ` [PATCH v3 bpf-next 2/4] selftests/bpf: add benchmark runner infrastructure Andrii Nakryiko
2020-05-13  1:09   ` Yonghong Song
2020-05-12 19:24 ` [PATCH v3 bpf-next 3/4] selftest/bpf: fmod_ret prog and implement test_overhead as part of bench Andrii Nakryiko
2020-05-13  1:10   ` Yonghong Song
2020-05-12 19:24 ` [PATCH v3 bpf-next 4/4] selftest/bpf: add BPF triggering benchmark Andrii Nakryiko
2020-05-13 19:23 ` Alexei Starovoitov [this message]

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=CAADnVQ+VdbzyRh0vUAZb4CaAUa9yncwSudswXozD+eS17yRT4Q@mail.gmail.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=ast@fb.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.