[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168204421944.9555.9530880882119320000.git-patchwork-notify@kernel.org>
Date: Fri, 21 Apr 2023 02:30:19 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, jbrouer@...hat.com, hawk@...nel.org,
ilias.apalodimas@...aro.org, tariqt@...dia.com
Subject: Re: [PATCH net-next] page_pool: unlink from napi during destroy
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 19 Apr 2023 11:20:06 -0700 you wrote:
> Jesper points out that we must prevent recycling into cache
> after page_pool_destroy() is called, because page_pool_destroy()
> is not synchronized with recycling (some pages may still be
> outstanding when destroy() gets called).
>
> I assumed this will not happen because NAPI can't be scheduled
> if its page pool is being destroyed. But I missed the fact that
> NAPI may get reused. For instance when user changes ring configuration
> driver may allocate a new page pool, stop NAPI, swap, start NAPI,
> and then destroy the old pool. The NAPI is running so old page
> pool will think it can recycle to the cache, but the consumer
> at that point is the destroy() path, not NAPI.
>
> [...]
Here is the summary with links:
- [net-next] page_pool: unlink from napi during destroy
https://git.kernel.org/netdev/net-next/c/dd64b232deb8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists