All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	kernelxing@tencent.com
Subject: Re: [PATCH v4 net-next] net: advance skb_defer_disable_key check in napi_consume_skb
Date: Tue, 07 Apr 2026 01:40:23 +0000	[thread overview]
Message-ID: <177552602370.3334922.4335754307864094547.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260402034114.65766-1-kerneljasonxing@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  2 Apr 2026 11:41:14 +0800 you wrote:
> From: Jason Xing <kernelxing@tencent.com>
> 
> When net.core.skb_defer_max is adjusted to zero, napi_consume_skb()
> shouldn't go into that deeper in skb_attempt_defer_free() because it adds
> an additional pair of local_bh_enable/disable() which is evidently not
> needed. Advancing the check of the static key saves more cycles and
> benefits non defer case.
> 
> [...]

Here is the summary with links:
  - [v4,net-next] net: advance skb_defer_disable_key check in napi_consume_skb
    https://git.kernel.org/netdev/net-next/c/8a4e3ab61d49

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-04-07  1:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  3:41 [PATCH v4 net-next] net: advance skb_defer_disable_key check in napi_consume_skb Jason Xing
2026-04-07  1:40 ` 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=177552602370.3334922.4335754307864094547.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kerneljasonxing@gmail.com \
    --cc=kernelxing@tencent.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.