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, netdev@vger.kernel.org, eric.dumazet@gmail.com,
dsahern@kernel.org
Subject: Re: [PATCH net-next 0/2] inet: ping: remove extra skb_clone()/consume_skb()
Date: Fri, 28 Feb 2025 22:50:34 +0000 [thread overview]
Message-ID: <174078303499.2301678.16469844740155000633.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250226183437.1457318-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Feb 2025 18:34:35 +0000 you wrote:
> First patch in the series moves ICMP_EXT_ECHOREPLY handling in icmp_rcv()
> to prepare the second patch.
>
> The second patch removes one skb_clone()/consume_skb() pair
> when processing ICMP_EXT_REPLY packets. Some people
> use hundreds of "ping -fq ..." to stress hosts :)
>
> [...]
Here is the summary with links:
- [net-next,1/2] ipv4: icmp: do not process ICMP_EXT_ECHOREPLY for broadcast/multicast addresses
https://git.kernel.org/netdev/net-next/c/daeb6a8f3b00
- [net-next,2/2] inet: ping: avoid skb_clone() dance in ping_rcv()
https://git.kernel.org/netdev/net-next/c/a7e38208fe71
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:[~2025-02-28 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 18:34 [PATCH net-next 0/2] inet: ping: remove extra skb_clone()/consume_skb() Eric Dumazet
2025-02-26 18:34 ` [PATCH net-next 1/2] ipv4: icmp: do not process ICMP_EXT_ECHOREPLY for broadcast/multicast addresses Eric Dumazet
2025-02-28 16:28 ` David Ahern
2025-02-26 18:34 ` [PATCH net-next 2/2] inet: ping: avoid skb_clone() dance in ping_rcv() Eric Dumazet
2025-02-28 16:30 ` David Ahern
2025-02-28 22: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=174078303499.2301678.16469844740155000633.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=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.