lkml.org 
[lkml]   [2023]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [EXT] Re: [PATCH net-next] page_pool: Clamp ring size to 32K
Date
> From: Jesper Dangaard Brouer <hawk@kernel.org>
> Sent: Tuesday, August 8, 2023 1:42 AM
> As a temporary solution, I'm actually fine with capping at 32k.
> Driver developer loose some feedback control, but perhaps that is okay, if
> we can agree that the net-core should control tuning this anyhow.


Capping will never let user know that memory is unnecessarily wasted as there is not much
Correlation between ring size and page pool size. I would prefer not setting pool->p.pool_size in
Octeontx2 (pool->p.pool_size = 0 ) driver and let page pool infra decide on that. Is this change acceptable ?
100G link burst traffic would be able to handle with 1024 page pool size, do we have any data with any other driver ?

-Ratheesh
\
 
 \ /
  Last update: 2023-08-08 04:27    [W:0.078 / U:0.048 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site