From: "Björn Töpel" <bjorn@kernel.org>
To: Stanislav Fomichev <sdf.kernel@gmail.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next v3 4/4] selftests: drv-net: measure devmem performance with kperf
Date: Tue, 03 Nov 2026 06:05:23 +0100 [thread overview]
Message-ID: <87wlqu33os.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <20261102190827.989117-5-sdf@fomichev.me>
Stanislav Fomichev <sdf.kernel@gmail.com> writes:
> Add a separate udmabuf-backed devmem performance test using KperfRunner.
> Keep correctness cases in drivers/net/hw. Skip the test when kperf or
> /dev/udmabuf is missing, and fail it when the kperf run fails.
>
> Example metric output:
>
> # # ktap-metric-json: {"goal":"higher","name":"throughput","value":389.127}
>
> Signed-off-by: Stanislav Fomichev <sdf@fomichev.me>
Reviewed-by: Björn Töpel <bjorn@kernel.org>
prev parent reply other threads:[~2026-11-03 5:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 19:08 [PATCH net-next v3 0/4] selftests: net: add performance metric reporting Stanislav Fomichev
2026-11-02 19:08 ` [PATCH net-next v3 1/4] selftests: net: py: add metric output Stanislav Fomichev
2026-11-03 4:54 ` Björn Töpel
2026-11-02 19:08 ` [PATCH net-next v3 2/4] selftests: drv-net: add an iperf performance test Stanislav Fomichev
2026-11-03 5:02 ` Björn Töpel
2026-11-03 19:10 ` Stanislav Fomichev
2026-11-02 19:08 ` [PATCH net-next v3 3/4] selftests: drv-net: add a kperf runner Stanislav Fomichev
2026-11-03 5:03 ` Björn Töpel
2026-11-02 19:08 ` [PATCH net-next v3 4/4] selftests: drv-net: measure devmem performance with kperf Stanislav Fomichev
2026-11-03 5:05 ` Björn Töpel [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=87wlqu33os.fsf@all.your.base.are.belong.to.us \
--to=bjorn@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