All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, dsahern@kernel.org, jamie.bainbridge@gmail.com,
	rawal.abhishek92@gmail.com, netdev@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next 0/9] ipv6: snmp: avoid performance issue with RATELIMITHOST
Date: Tue, 09 Sep 2025 01:30:35 +0000	[thread overview]
Message-ID: <175738143575.108077.2162956329371519452.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250905165813.1470708-1-edumazet@google.com>

Hello:

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

On Fri,  5 Sep 2025 16:58:04 +0000 you wrote:
> Addition of ICMP6_MIB_RATELIMITHOST in commit d0941130c9351
> ("icmp: Add counters for rate limits") introduced a performance
> drop in case of DOS (like receiving UDP packets
> to closed ports).
> 
> Per netns ICMP6_MIB_RATELIMITHOST tracking uses per-cpu
> storage and is enough, we do not need per-device and slow tracking
> for this metric.
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/9] ipv6: snmp: remove icmp6type2name[]
    https://git.kernel.org/netdev/net-next/c/b7fe8c1be776
  - [v2,net-next,2/9] ipv6: snmp: do not use SNMP_MIB_SENTINEL anymore
    https://git.kernel.org/netdev/net-next/c/ceac1fb2290d
  - [v2,net-next,3/9] ipv6: snmp: do not track per idev ICMP6_MIB_RATELIMITHOST
    https://git.kernel.org/netdev/net-next/c/2fab94bcf313
  - [v2,net-next,4/9] ipv4: snmp: do not use SNMP_MIB_SENTINEL anymore
    https://git.kernel.org/netdev/net-next/c/b7b74953f834
  - [v2,net-next,5/9] mptcp: snmp: do not use SNMP_MIB_SENTINEL anymore
    https://git.kernel.org/netdev/net-next/c/35cb2da0abaf
  - [v2,net-next,6/9] sctp: snmp: do not use SNMP_MIB_SENTINEL anymore
    https://git.kernel.org/netdev/net-next/c/52a33cae6a6f
  - [v2,net-next,7/9] tls: snmp: do not use SNMP_MIB_SENTINEL anymore
    https://git.kernel.org/netdev/net-next/c/3a951f95202c
  - [v2,net-next,8/9] xfrm: snmp: do not use SNMP_MIB_SENTINEL anymore
    https://git.kernel.org/netdev/net-next/c/c73d583e7008
  - [v2,net-next,9/9] net: snmp: remove SNMP_MIB_SENTINEL
    https://git.kernel.org/netdev/net-next/c/20d3d2681544

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



      parent reply	other threads:[~2025-09-09  1:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 16:58 [PATCH v2 net-next 0/9] ipv6: snmp: avoid performance issue with RATELIMITHOST Eric Dumazet
2025-09-05 16:58 ` [PATCH v2 net-next 1/9] ipv6: snmp: remove icmp6type2name[] Eric Dumazet
2025-09-08 13:49   ` Sabrina Dubroca
2025-09-05 16:58 ` [PATCH v2 net-next 2/9] ipv6: snmp: do not use SNMP_MIB_SENTINEL anymore Eric Dumazet
2025-09-08 13:49   ` Sabrina Dubroca
2025-09-05 16:58 ` [PATCH v2 net-next 3/9] ipv6: snmp: do not track per idev ICMP6_MIB_RATELIMITHOST Eric Dumazet
2025-09-05 16:58 ` [PATCH v2 net-next 4/9] ipv4: snmp: do not use SNMP_MIB_SENTINEL anymore Eric Dumazet
2025-09-08 13:54   ` Sabrina Dubroca
2025-09-05 16:58 ` [PATCH v2 net-next 5/9] mptcp: " Eric Dumazet
2025-09-06 12:59   ` Matthieu Baerts
2025-09-05 16:58 ` [PATCH v2 net-next 6/9] sctp: " Eric Dumazet
2025-09-08 13:56   ` Sabrina Dubroca
2025-09-08 15:29   ` Xin Long
2025-09-05 16:58 ` [PATCH v2 net-next 7/9] tls: " Eric Dumazet
2025-09-08 13:58   ` Sabrina Dubroca
2025-09-05 16:58 ` [PATCH v2 net-next 8/9] xfrm: " Eric Dumazet
2025-09-08 14:12   ` Sabrina Dubroca
2025-09-05 16:58 ` [PATCH v2 net-next 9/9] net: snmp: remove SNMP_MIB_SENTINEL Eric Dumazet
2025-09-08 14:18   ` Sabrina Dubroca
2025-09-09  1:30 ` 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=175738143575.108077.2162956329371519452.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=jamie.bainbridge@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rawal.abhishek92@gmail.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.