Re: [PATCH net-next] eth: bnxt: take page size into account for page pool recycling rings

[Jakub Kicinski <kuba@kernel.org>]

On Thu, 26 Jun 2025 14:52:17 -0700 Michael Chan wrote:
> >  {
> > +       const unsigned int agg_size_fac = PAGE_SIZE / BNXT_RX_PAGE_SIZE;
> > +       const unsigned int rx_size_fac = PAGE_SIZE / SZ_4K;
> >         struct page_pool_params pp = { 0 };
> >         struct page_pool *pool;
> >
> > -       pp.pool_size = bp->rx_agg_ring_size;
> > +       pp.pool_size = bp->rx_agg_ring_size / agg_size_fac;  
> 
> The bp->rx_agg_ring_size has already taken the system PAGE_SIZE into
> consideration to some extent in bnxt_set_ring_params().  The
> jumbo_factor and agg_factor will be smaller when PAGE_SIZE is larger.
> Will this overcompensate?

My understanding is basically that bnxt_set_ring_params() operates
on BNXT_RX_PAGE_SIZE so it takes care of 4k .. 32k range pretty well.
But for 64k pages we will use 32k buffers, so 2 agg ring entries
per system page. If our heuristic is that we want the same number
of pages on the device ring as in the pp cache we should divide 
the cache size by two. Hope that makes sense.

My initial temptation was to say that agg ring is always shown to 
the user in 4kB units, regardless of system page. The driver would
divide and multiply the parameter in the ethtool callbacks. Otherwise
even with this patch existing configs for bnxt have to be adjusted
based on system page size :( But I suspect you may have existing users
on systems with 64kB pages, so this would be too risky? WDYT?