From: Jakub Kicinski <kuba@kernel•org>
To: Nimrod Oren <noren@nvidia•com>
Cc: Jesper Dangaard Brouer <hawk@kernel•org>,
Ilias Apalodimas <ilias.apalodimas@linaro•org>,
"David S. Miller" <davem@davemloft•net>,
"Eric Dumazet" <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>, Simon Horman <horms@kernel•org>,
<netdev@vger•kernel.org>, <linux-kernel@vger•kernel.org>,
Gal Pressman <gal@nvidia•com>,
Dragos Tatulea <dtatulea@nvidia•com>,
Tariq Toukan <tariqt@nvidia•com>
Subject: Re: [RFC net-next] net: page_pool: cap alloc cache size and refill by pool ring size
Date: Tue, 24 Feb 2026 15:39:59 -0800 [thread overview]
Message-ID: <20260224153959.377a8e32@kernel.org> (raw)
In-Reply-To: <20260223092410.2149014-1-noren@nvidia.com>
On Mon, 23 Feb 2026 11:24:10 +0200 Nimrod Oren wrote:
> I'd appreciate feedback on:
> * Whether this per-pool cache capping approach makes sense
> * If so, which option is preferable
> * Any alternative suggestions to better cap/scale the page_pool cache
> parameters for large pages
I'd simply change the defines based on PAGE_SIZE. The allocation batch
size has nothing to do with the ring size, it's just amortizing
allocations within a single NAPI cycle.
#if PAGE_SIZE >= 64K
#define PP_ALLOC_CACHE_REFILL 16
#elif PAGE_SIZE >= 16K
#define PP_ALLOC_CACHE_REFILL 32
#else
#define PP_ALLOC_CACHE_REFILL 64
#endif
#define PP_ALLOC_CACHE_SIZE (PP_ALLOC_CACHE_REFILL * 2)
next prev parent reply other threads:[~2026-02-24 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 9:24 [RFC net-next] net: page_pool: cap alloc cache size and refill by pool ring size Nimrod Oren
2026-02-24 23:39 ` Jakub Kicinski [this message]
2026-02-26 15:28 ` Nimrod Oren
2026-02-26 16:56 ` Jakub Kicinski
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=20260224153959.377a8e32@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dtatulea@nvidia$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=gal@nvidia$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=horms@kernel$(echo .)org \
--cc=ilias.apalodimas@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=noren@nvidia$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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