From: Jakub Kicinski <kuba@kernel.org>
To: Mina Almasry <almasrymina@google.com>
Cc: patchwork-bot+netdevbpf@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
hawk@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
ilias.apalodimas@linaro.org, toke@toke.dk
Subject: Re: [PATCH net-next v5] page_pool: import Jesper's page_pool benchmark
Date: Wed, 25 Jun 2025 17:03:05 -0700 [thread overview]
Message-ID: <20250625170305.40d8c27a@kernel.org> (raw)
In-Reply-To: <CAHS8izMPWjmxLWJr+BSqd5jamsFHDOm71NkG7fmm-78SkLxQTg@mail.gmail.com>
On Wed, 25 Jun 2025 16:45:49 -0700 Mina Almasry wrote:
> Thank you for merging this. Kinda of a noob question: does this merge
> mean that nipa will run this on new submitted patches already? Or do
> I/someone need to do something to enable that? I've been clicking on
> the contest for new patches like so:
>
> https://netdev.bots.linux.dev/contest.html?pw-n=0&branch=net-next-2025-06-25--21-00
>
> But I don't see this benchmark being run anywhere. I looked for docs
> that already cover this but I couldn't find any.
Right now to add a new TARGET one needs to have SSH access to the
systems that run the tests :( The process of adding a runner is not
automated. But this will probably need even more work because it's
a performance test. We'd need some way of tracking numerical values
and detecting regressions?
We have a vague plan of moving NIPA out of Meta owned systems.
We may want to wait for that before we tackle performance-like tests.
next prev parent reply other threads:[~2025-06-26 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 18:15 [PATCH net-next v5] page_pool: import Jesper's page_pool benchmark Mina Almasry
2025-06-20 7:49 ` Toke Høiland-Jørgensen
2025-06-24 1:20 ` patchwork-bot+netdevbpf
2025-06-25 23:45 ` Mina Almasry
2025-06-26 0:03 ` Jakub Kicinski [this message]
2025-06-26 0:22 ` Mina Almasry
2025-06-26 15:23 ` Jakub Kicinski
2025-06-26 16:30 ` Mina Almasry
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=20250625170305.40d8c27a@kernel.org \
--to=kuba@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=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox