From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Mina Almasry <almasrymina@google.com>,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "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>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH net-next v1 2/2] selftests: pp-bench: remove page_pool_put_page wrapper
Date: Tue, 1 Jul 2025 17:49:14 +0200 [thread overview]
Message-ID: <3bd1e6ef-cf3d-4ace-85e8-7f98cf92cc1f@kernel.org> (raw)
In-Reply-To: <20250627200501.1712389-2-almasrymina@google.com>
On 27/06/2025 22.04, Mina Almasry wrote:
> Minor cleanup: remove the pointless looking _ wrapper around
> page_pool_put_page, and just do the call directly.
>
> Signed-off-by: Mina Almasry <almasrymina@google.com>
> ---
> .../net/bench/page_pool/bench_page_pool_simple.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/tools/testing/selftests/net/bench/page_pool/bench_page_pool_simple.c b/tools/testing/selftests/net/bench/page_pool/bench_page_pool_simple.c
> index 1cd3157fb6a9..cb6468adbda4 100644
> --- a/tools/testing/selftests/net/bench/page_pool/bench_page_pool_simple.c
> +++ b/tools/testing/selftests/net/bench/page_pool/bench_page_pool_simple.c
> @@ -16,12 +16,6 @@
> static int verbose = 1;
> #define MY_POOL_SIZE 1024
>
> -static void _page_pool_put_page(struct page_pool *pool, struct page *page,
> - bool allow_direct)
> -{
> - page_pool_put_page(pool, page, -1, allow_direct);
> -}
> -
> /* Makes tests selectable. Useful for perf-record to analyze a single test.
> * Hint: Bash shells support writing binary number like: $((2#101010)
> *
> @@ -121,7 +115,7 @@ static void pp_fill_ptr_ring(struct page_pool *pp, int elems)
> for (i = 0; i < elems; i++)
> array[i] = page_pool_alloc_pages(pp, gfp_mask);
> for (i = 0; i < elems; i++)
> - _page_pool_put_page(pp, array[i], false);
> + page_pool_put_page(pp, array[i], -1, false);
>
> kfree(array);
> }
> @@ -180,14 +174,14 @@ static int time_bench_page_pool(struct time_bench_record *rec, void *data,
>
> } else if (type == type_ptr_ring) {
> /* Normal return path */
> - _page_pool_put_page(pp, page, false);
> + page_pool_put_page(pp, page, -1, false);
>
> } else if (type == type_page_allocator) {
> /* Test if not pages are recycled, but instead
> * returned back into systems page allocator
> */
> get_page(page); /* cause no-recycling */
> - _page_pool_put_page(pp, page, false);
> + page_pool_put_page(pp, page, -1, false);
> put_page(page);
The get_page() + put_page() trick is a fairly ugly workaround that I
added when Jakub removed page_pool_release_page() in commit 535b9c61bdef
("net: page_pool: hide page_pool_release_page()").
These extra refcnt increments will make the test slower, but if we are
just aware of this, then we can still compare incremental changes.
Acked-by: Jesper Dangaard Brouer <hawk@kernel.org>
> } else {
> BUILD_BUG();
next prev parent reply other threads:[~2025-07-01 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 20:04 [PATCH net-next v1 1/2] selftests: pp-bench: remove unneeded linux/version.h Mina Almasry
2025-06-27 20:04 ` [PATCH net-next v1 2/2] selftests: pp-bench: remove page_pool_put_page wrapper Mina Almasry
2025-06-30 10:02 ` Simon Horman
2025-06-30 12:33 ` Toke Høiland-Jørgensen
2025-06-30 15:00 ` Ilias Apalodimas
2025-07-01 15:49 ` Jesper Dangaard Brouer [this message]
2025-06-30 10:00 ` [PATCH net-next v1 1/2] selftests: pp-bench: remove unneeded linux/version.h Simon Horman
2025-06-30 12:33 ` Toke Høiland-Jørgensen
2025-06-30 14:19 ` Ilias Apalodimas
2025-07-01 8:56 ` Jesper Dangaard Brouer
2025-07-02 0:50 ` patchwork-bot+netdevbpf
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=3bd1e6ef-cf3d-4ace-85e8-7f98cf92cc1f@kernel.org \
--to=hawk@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=lkp@intel.com \
--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).