[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174010204326.1539943.669802709586927809.git-patchwork-notify@kernel.org>
Date: Fri, 21 Feb 2025 01:40:43 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Kohei Enju <enjuk@...zon.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
kuniyu@...zon.com, gnaaman@...venets.com, joel.granados@...nel.org,
lizetao1@...wei.com, cl@...ux.com, penberg@...nel.org, rientjes@...gle.com,
iamjoonsoo.kim@....com, akpm@...ux-foundation.org, vbabka@...e.cz,
roman.gushchin@...ux.dev, 42.hyeyoo@...il.com, kohei.enju@...il.com
Subject: Re: [PATCH net-next v2] neighbour: Replace kvzalloc() with kzalloc() when
GFP_ATOMIC is specified
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 19 Feb 2025 19:22:27 +0900 you wrote:
> kzalloc() uses page allocator when size is larger than
> KMALLOC_MAX_CACHE_SIZE, so the intention of commit ab101c553bc1
> ("neighbour: use kvzalloc()/kvfree()") can be achieved by using kzalloc().
>
> When using GFP_ATOMIC, kvzalloc() only tries the kmalloc path,
> since the vmalloc path does not support the flag.
> In this case, kvzalloc() is equivalent to kzalloc() in that neither try
> the vmalloc path, so this replacement brings no functional change.
> This is primarily a cleanup change, as the original code functions
> correctly.
>
> [...]
Here is the summary with links:
- [net-next,v2] neighbour: Replace kvzalloc() with kzalloc() when GFP_ATOMIC is specified
https://git.kernel.org/netdev/net-next/c/ef75d8343bc1
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