From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, puranjay12@gmail.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, mykyta.yatsenko5@gmail.com,
feichen@meta.com, taragrawal@meta.com, ndixit@meta.com,
tehnerd@tehnerd.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 0/7] selftests/bpf: Add XDP load-balancer benchmark
Date: Mon, 11 May 2026 23:00:15 +0000 [thread overview]
Message-ID: <177854041580.2496500.4714535434277470100.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260427232313.1582588-1-puranjay@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 27 Apr 2026 16:22:57 -0700 you wrote:
> Changelog:
> RFC: https://lore.kernel.org/all/20260420111726.2118636-1-puranjay@kernel.org/
> Changes in v1:
> - Replace bpf_get_cpu_time_counter() with bpf_ktime_get_ns()
> - Replace bpf_repeat() with plain for loop and may_goto
> - Refactor collect_measurements() to reuse bench_force_done()
> - Remove histogram, verbose calibration output, and per-scenario status prints
> - Trim run script table to p50/stddev/p99
> - Set env.quiet when --machine-readable is passed
> - Add || true to run script benchmark invocation for set -e safety
> - Add bpf-nop benchmark as timing overhead baseline (patch 3)
> - Use named struct for LRU inner map to fix build on older toolchains
>
> [...]
Here is the summary with links:
- [bpf-next,1/7] selftests/bpf: Add bench_force_done() for early benchmark completion
https://git.kernel.org/bpf/bpf-next/c/2b6f0a1e4c9e
- [bpf-next,2/7] selftests/bpf: Add BPF batch-timing library
https://git.kernel.org/bpf/bpf-next/c/08158c111d7d
- [bpf-next,3/7] selftests/bpf: Add bpf-nop benchmark for timing overhead baseline
https://git.kernel.org/bpf/bpf-next/c/dcf11479c2a8
- [bpf-next,4/7] selftests/bpf: Add XDP load-balancer common definitions
https://git.kernel.org/bpf/bpf-next/c/6b4003a7b333
- [bpf-next,5/7] selftests/bpf: Add XDP load-balancer BPF program
https://git.kernel.org/bpf/bpf-next/c/4b4f2229104c
- [bpf-next,6/7] selftests/bpf: Add XDP load-balancer benchmark driver
https://git.kernel.org/bpf/bpf-next/c/a4b5ba8187cb
- [bpf-next,7/7] selftests/bpf: Add XDP load-balancer benchmark run script
https://git.kernel.org/bpf/bpf-next/c/51312b6360a9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-11 23:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 23:22 [PATCH bpf-next 0/7] selftests/bpf: Add XDP load-balancer benchmark Puranjay Mohan
2026-04-27 23:22 ` [PATCH bpf-next 1/7] selftests/bpf: Add bench_force_done() for early benchmark completion Puranjay Mohan
2026-04-27 23:39 ` sashiko-bot
2026-04-28 0:05 ` bot+bpf-ci
2026-04-28 9:15 ` Puranjay Mohan
2026-04-27 23:22 ` [PATCH bpf-next 2/7] selftests/bpf: Add BPF batch-timing library Puranjay Mohan
2026-04-28 0:12 ` sashiko-bot
2026-04-28 0:18 ` bot+bpf-ci
2026-04-28 9:23 ` Puranjay Mohan
2026-04-27 23:23 ` [PATCH bpf-next 3/7] selftests/bpf: Add bpf-nop benchmark for timing overhead baseline Puranjay Mohan
2026-04-27 23:23 ` [PATCH bpf-next 4/7] selftests/bpf: Add XDP load-balancer common definitions Puranjay Mohan
2026-04-28 0:05 ` bot+bpf-ci
2026-04-28 0:38 ` sashiko-bot
2026-04-28 9:29 ` Puranjay Mohan
2026-04-27 23:23 ` [PATCH bpf-next 5/7] selftests/bpf: Add XDP load-balancer BPF program Puranjay Mohan
2026-04-28 0:18 ` bot+bpf-ci
2026-04-28 1:05 ` sashiko-bot
2026-04-28 9:30 ` Puranjay Mohan
2026-04-27 23:23 ` [PATCH bpf-next 6/7] selftests/bpf: Add XDP load-balancer benchmark driver Puranjay Mohan
2026-04-28 0:05 ` bot+bpf-ci
2026-04-28 1:29 ` sashiko-bot
2026-04-28 9:33 ` Puranjay Mohan
2026-04-27 23:23 ` [PATCH bpf-next 7/7] selftests/bpf: Add XDP load-balancer benchmark run script Puranjay Mohan
2026-04-28 2:03 ` sashiko-bot
2026-05-11 22:58 ` [PATCH bpf-next 0/7] selftests/bpf: Add XDP load-balancer benchmark Alexei Starovoitov
2026-05-11 23:00 ` patchwork-bot+netdevbpf [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=177854041580.2496500.4714535434277470100.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=feichen@meta.com \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=ndixit@meta.com \
--cc=puranjay12@gmail.com \
--cc=puranjay@kernel.org \
--cc=taragrawal@meta.com \
--cc=tehnerd@tehnerd.com \
/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