[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <095e7aac-4539-4f0e-b698-dd7b3f95f1dd@intel.com>
Date: Tue, 15 Oct 2024 12:26:54 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Praveen Kaligineedi <pkaligineedi@...gle.com>, <netdev@...r.kernel.org>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
<pabeni@...hat.com>, <willemb@...gle.com>, <jeroendb@...gle.com>,
<shailend@...gle.com>, <hramamurthy@...gle.com>, <ziweixiao@...gle.com>,
<shannon.nelson@....com>
Subject: Re: [PATCH net-next v3 0/3] gve: adopt page pool
On 10/14/2024 1:21 PM, Praveen Kaligineedi wrote:
> From: Harshitha Ramamurthy <hramamurthy@...gle.com>
>
> This patchset implements page pool support for gve.
> The first patch deals with movement of code to make
> page pool adoption easier in the next patch. The
> second patch adopts the page pool API. The third patch
> adds basic per queue stats which includes page pool
> allocation failures as well.
>
> Changes in v3:
> -Add patch 3 for per queue stats to track page pool alloc
> failures (Jakub Kicinski)
> -Remove ethtool stat for page pool alloc failures in patch 2
> (Jakub Kicinski)
>
> Changes in v2:
> -Set allow_direct parameter to true in napi context and false
> in others (Shannon Nelson)
> -Set the napi pointer in page pool params (Jakub Kicinski)
> -Track page pool alloc failures per ring (Jakub Kicinski)
> -Don't exceed 80 char limit (Jakub Kicinski)
>
Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
Powered by blists - more mailing lists