From: patchwork-bot+netdevbpf@kernel•org
To: Jakub Kicinski <kuba@kernel•org>
Cc: davem@davemloft•net, netdev@vger•kernel.org, edumazet@google•com,
pabeni@redhat•com, aleksander.lobakin@intel•com,
alexs@kernel•org, siyanteng@loongson•cn,
jesse.brandeburg@intel•com, anthony.l.nguyen@intel•com,
alexandre.torgue@foss•st.com, joabreu@synopsys•com,
mcoquelin.stm32@gmail•com, intel-wired-lan@lists•osuosl.org
Subject: Re: [PATCH net-next v2] net: remove gfp_mask from napi_alloc_skb()
Date: Fri, 29 Mar 2024 01:50:29 +0000 [thread overview]
Message-ID: <171167702984.13430.7602410766409441835.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240327040213.3153864-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Tue, 26 Mar 2024 21:02:12 -0700 you wrote:
> __napi_alloc_skb() is napi_alloc_skb() with the added flexibility
> of choosing gfp_mask. This is a NAPI function, so GFP_ATOMIC is
> implied. The only practical choice the caller has is whether to
> set __GFP_NOWARN. But that's a false choice, too, allocation failures
> in atomic context will happen, and printing warnings in logs,
> effectively for a packet drop, is both too much and very likely
> non-actionable.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: remove gfp_mask from napi_alloc_skb()
https://git.kernel.org/netdev/net-next/c/6e9b01909a81
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-29 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 4:02 [PATCH net-next v2] net: remove gfp_mask from napi_alloc_skb() Jakub Kicinski
2024-03-28 11:32 ` Simon Horman
2024-03-28 11:48 ` Eric Dumazet
2024-03-29 1:50 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171167702984.13430.7602410766409441835.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=aleksander.lobakin@intel$(echo .)com \
--cc=alexandre.torgue@foss$(echo .)st.com \
--cc=alexs@kernel$(echo .)org \
--cc=anthony.l.nguyen@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=joabreu@synopsys$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=mcoquelin.stm32@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=siyanteng@loongson$(echo .)cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox