All of lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH net-next] net: skbuff: update and rename __kfree_skb_defer()
Date: Fri, 21 Apr 2023 02:50:19 +0000	[thread overview]
Message-ID: <168204541957.19656.7376141255783199267.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230420020005.815854-1-kuba@kernel.org>

Hello:

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

On Wed, 19 Apr 2023 19:00:05 -0700 you wrote:
> __kfree_skb_defer() uses the old naming where "defer" meant
> slab bulk free/alloc APIs. In the meantime we also made
> __kfree_skb_defer() feed the per-NAPI skb cache, which
> implies bulk APIs. So take away the 'defer' and add 'napi'.
> 
> While at it add a drop reason. This only matters on the
> tx_action path, if the skb has a frag_list. But getting
> rid of a SKB_DROP_REASON_NOT_SPECIFIED seems like a net
> benefit so why not.
> 
> [...]

Here is the summary with links:
  - [net-next] net: skbuff: update and rename __kfree_skb_defer()
    https://git.kernel.org/netdev/net-next/c/8fa66e4a1bdd

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



      parent reply	other threads:[~2023-04-21  2:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20  2:00 [PATCH net-next] net: skbuff: update and rename __kfree_skb_defer() Jakub Kicinski
2023-04-20 15:06 ` Alexander Lobakin
2023-04-21  2: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=168204541957.19656.7376141255783199267.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.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.