From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc: "Jesper Dangaard Brouer" <hawk@kernel.org>,
"Mina Almasry" <almasrymina@google.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Shuah Khan" <shuah@kernel.org>
Subject: Re: [PATCH RFC net-next v2] page_pool: import Jesper's page_pool benchmark
Date: Tue, 10 Jun 2025 17:33:09 -0300 [thread overview]
Message-ID: <aEiWhUDsFskkcv46@x1> (raw)
In-Reply-To: <CAC_iWjJcC7sK+71GVZHrXzPL=e3N_uFnKPnhSEi=PJkPwUywsA@mail.gmail.com>
On Tue, Jun 10, 2025 at 10:41:49AM +0300, Ilias Apalodimas wrote:
> On Wed, 4 Jun 2025 at 11:39, Jesper Dangaard Brouer <hawk@kernel.org> wrote:
> > Okay, I think Ilias'es comment[1] and ACK convinced me, let us merge
> > this as-is. We have been asking people to run it over several years
> > before accepting patches. We shouldn't be pointing people to use
> > out-of-tree tests for accepting patches.
> > It is not perfect, but it have served us well for benchmarking in the
> > last approx 10 years (5 years for page_pool test). It is isolated as a
> > selftest under (tools/testing/selftests/net/bench/page_pool/).
> > Realistically we are all too busy inventing a new "perfect" benchmark
> > for page_pool. That said, I do encourage others with free cycles to
> > integrated a better benchmark test into `perf bench`. Then we can just
> > remove this module again.
> I'll spend some time looking at acme comments. They seem to be moving
> towards the right direction
Glad that you think that way, and to add another perspective, 'perf
test' and 'perf bench' goals are to run in any kernel, not just some
specific one where a regression was fixed, so people running plain 'perf
bench' will run whatever tests we add and thus widen the tester base for
the benchmarks in there.
Being able to combine 'perf trace perf bench', 'perf stat perf bench',
etc is something common and powerful.
But then the most important thing is to have actionable and expertly
written benchmarks in place, that have been in use for a long time, in
whatever form :-)
- Arnaldo
prev parent reply other threads:[~2025-06-10 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 3:43 [PATCH RFC net-next v2] page_pool: import Jesper's page_pool benchmark Mina Almasry
2025-05-26 12:51 ` Toke Høiland-Jørgensen
2025-05-27 20:07 ` Mina Almasry
2025-05-28 9:28 ` Toke Høiland-Jørgensen
2025-05-28 13:51 ` Arnaldo Carvalho de Melo
2025-05-28 17:14 ` Toke Høiland-Jørgensen
2025-06-04 7:04 ` Ilias Apalodimas
2025-05-28 19:46 ` Mina Almasry
2025-06-04 8:39 ` Jesper Dangaard Brouer
2025-06-10 7:41 ` Ilias Apalodimas
2025-06-10 20:33 ` Arnaldo Carvalho de Melo [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=aEiWhUDsFskkcv46@x1 \
--to=acme@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=toke@redhat.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;
as well as URLs for NNTP newsgroup(s).