All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Radu Rendec <rrendec@redhat.com>
Cc: razor@blackwall.org, idosch@idosch.org, roopa@nvidia.com,
	bridge@lists.linux.dev, netdev@vger.kernel.org, horms@kernel.org,
	pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
	davem@davemloft.net
Subject: Re: [PATCH net-next v3 0/2] net/bridge: Add skb drop reasons to the most common drop points
Date: Mon, 23 Dec 2024 18:40:46 +0000	[thread overview]
Message-ID: <173497924627.3927205.16787669909128619677.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241219163606.717758-1-rrendec@redhat.com>

Hello:

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

On Thu, 19 Dec 2024 11:36:04 -0500 you wrote:
> The bridge input code may drop frames for various reasons and at various
> points in the ingress handling logic. Currently kfree_skb() is used
> everywhere, and therefore no drop reason is specified. Add drop reasons
> to the most common drop points.
> 
> The purpose of this series is to address the most common drop points on
> the bridge ingress path. It does not exhaustively add drop reasons to
> the entire bridge code. The intention here is to incrementally add drop
> reasons to the rest of the bridge code in follow up patches.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/2] net: vxlan: rename SKB_DROP_REASON_VXLAN_NO_REMOTE
    https://git.kernel.org/netdev/net-next/c/46e0ccfb88f0
  - [net-next,v3,2/2] net: bridge: add skb drop reasons to the most common drop points
    https://git.kernel.org/netdev/net-next/c/623e43c2f502

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



      parent reply	other threads:[~2024-12-23 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 16:36 [PATCH net-next v3 0/2] net/bridge: Add skb drop reasons to the most common drop points Radu Rendec
2024-12-19 16:36 ` [PATCH net-next v3 1/2] net: vxlan: rename SKB_DROP_REASON_VXLAN_NO_REMOTE Radu Rendec
2024-12-22  8:13   ` Ido Schimmel
2024-12-22  9:45   ` Nikolay Aleksandrov
2024-12-19 16:36 ` [PATCH net-next v3 2/2] net: bridge: add skb drop reasons to the most common drop points Radu Rendec
2024-12-22  8:15   ` Ido Schimmel
2024-12-22  9:46   ` Nikolay Aleksandrov
2024-12-23 18: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=173497924627.3927205.16787669909128619677.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bridge@lists.linux.dev \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@idosch.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.com \
    --cc=rrendec@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.