From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next v4 0/4] selftests: net: add performance metric reporting
Date: Tue, 17 Nov 2026 02:30:06 +0000 [thread overview]
Message-ID: <179488260653.297000.12268110044714000172.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111000246.962871-1-sdf@fomichev.me>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Nov 2026 16:02:42 -0800 you wrote:
> Let Python selftests report numeric measurements, so that CI can track
> the performance of drivers over time, and add two performance tests.
>
> ksft_metric() reports a measurement of the current test case, which is
> printed right away as JSON:
>
> # ktap-metric-json: {"goal":"higher","name":"throughput","value":389.127}
>
> [...]
Here is the summary with links:
- [net-next,v4,1/4] selftests: net: py: add metric output
https://git.kernel.org/netdev/net-next/c/d3def02d1d5f
- [net-next,v4,2/4] selftests: drv-net: add an iperf performance test
https://git.kernel.org/netdev/net-next/c/c1d2b8e89a29
- [net-next,v4,3/4] selftests: drv-net: add a kperf runner
https://git.kernel.org/netdev/net-next/c/d069373da963
- [net-next,v4,4/4] selftests: drv-net: measure devmem performance with kperf
https://git.kernel.org/netdev/net-next/c/a642edca4a88
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-11-17 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 0:02 [PATCH net-next v4 0/4] selftests: net: add performance metric reporting Stanislav Fomichev
2026-11-11 0:02 ` [PATCH net-next v4 1/4] selftests: net: py: add metric output Stanislav Fomichev
2026-11-13 6:03 ` netdev-bot+sashiko
2026-11-11 0:02 ` [PATCH net-next v4 2/4] selftests: drv-net: add an iperf performance test Stanislav Fomichev
2026-11-13 6:03 ` netdev-bot+sashiko
2026-11-11 0:02 ` [PATCH net-next v4 3/4] selftests: drv-net: add a kperf runner Stanislav Fomichev
2026-11-13 6:03 ` netdev-bot+sashiko
2026-11-11 0:02 ` [PATCH net-next v4 4/4] selftests: drv-net: measure devmem performance with kperf Stanislav Fomichev
2026-11-13 6:03 ` netdev-bot+sashiko
2026-11-17 2:30 ` 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=179488260653.297000.12268110044714000172.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.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