From: patchwork-bot+netdevbpf@kernel.org
To: Nimrod Oren <noren@nvidia.com>
Cc: hawk@kernel.org, ilias.apalodimas@linaro.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, gal@nvidia.com,
dtatulea@nvidia.com, tariqt@nvidia.com
Subject: Re: [PATCH net-next] net: page_pool: scale alloc cache with PAGE_SIZE
Date: Fri, 13 Mar 2026 02:50:23 +0000 [thread overview]
Message-ID: <177337022304.648356.2556762129398077891.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260309081301.103152-1-noren@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 9 Mar 2026 10:13:01 +0200 you wrote:
> The current page_pool alloc-cache size and refill values were chosen to
> match the NAPI budget and to leave headroom for XDP_DROP recycling.
> These fixed values do not scale well with large pages,
> as they significantly increase a given page_pool's memory footprint.
>
> Scale these values to better balance memory footprint across page sizes,
> while keeping behavior on 4KB-page systems unchanged.
>
> [...]
Here is the summary with links:
- [net-next] net: page_pool: scale alloc cache with PAGE_SIZE
https://git.kernel.org/netdev/net-next/c/15abbe7c8266
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-13 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 8:13 [PATCH net-next] net: page_pool: scale alloc cache with PAGE_SIZE Nimrod Oren
2026-03-12 0:56 ` Jakub Kicinski
2026-03-16 15:17 ` Jesper Dangaard Brouer
2026-03-13 2:50 ` patchwork-bot+netdevbpf [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=177337022304.648356.2556762129398077891.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.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=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.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