From: Jakub Kicinski <kuba@kernel.org>
To: Mina Almasry <almasrymina@google.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [PATCH RFC net-next v1] page_pool: import Jesper's page_pool benchmark
Date: Tue, 25 Mar 2025 15:38:54 -0700 [thread overview]
Message-ID: <20250325153854.4e3b6834@kernel.org> (raw)
In-Reply-To: <CAHS8izPTxxcQog3yA=wSyTn-B6jT2U3KsQDzYb4LDW546=uoDg@mail.gmail.com>
On Mon, 24 Mar 2025 13:21:53 -0700 Mina Almasry wrote:
> > Why not in tools/testing? I thought selftest infra supported modules.
>
> You must be referring to TEST_GEN_MODS_DIR? Yes, that seems better. We
> don't use it in tools/testing/selftests/net but it is used in
> tool/testing/selftests/mm and page_frag_test.ko is a very similar
> example. I can put it in tools/testing/selftests/net/page_pool_bench
> or something like that.
>
> Also I guess you're alluding that this benchmark should be a selftest
> as well, right? I can make it a selftest but probably for starters the
> test will run and output the perf data but will exit code 4 to skip,
> right? I'm not sure it is consistent enough to get pass/fail data from
> it. When I run it in my env it's mostly consistent but i'm not sure
> across evironments.
skip in KTAP is just pass + annotation.
I think we should be reporting pass + result.
I don't think a format for that has been chosen, so we can just pick
our own? :) We already use our own annotations like "# time=450ms"
Maybe report a "test case" for every datapoint we may want to track
and add "# perf=Xu" annotation, where X is the numeric result and u is
a unit (with an optional metric prefix)?
next prev parent reply other threads:[~2025-03-25 22:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 8:41 [PATCH RFC net-next v1] page_pool: import Jesper's page_pool benchmark Mina Almasry
2025-03-09 10:34 ` kernel test robot
2025-03-10 6:22 ` kernel test robot
2025-03-10 8:08 ` kernel test robot
2025-03-10 9:15 ` Toke Høiland-Jørgensen
2025-03-24 20:23 ` Mina Almasry
2025-03-24 22:11 ` Jesper Dangaard Brouer
2025-03-24 13:55 ` Jakub Kicinski
2025-03-24 20:21 ` Mina Almasry
2025-03-25 22:38 ` Jakub Kicinski [this message]
2025-03-24 22:34 ` Jesper Dangaard Brouer
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=20250325153854.4e3b6834@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=toke@toke.dk \
/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.