From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
ncardwell@google.com, kuniyu@amazon.com,
kerneljasonxing@gmail.com, horms@kernel.org,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/4] tcp: scale connect() under pressure
Date: Wed, 05 Mar 2025 02:00:34 +0000 [thread overview]
Message-ID: <174114003473.368364.10864738728714771230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250302124237.3913746-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 2 Mar 2025 12:42:33 +0000 you wrote:
> Adoption of bhash2 in linux-6.1 made some operations almost twice
> more expensive, because of additional locks.
>
> This series adds RCU in __inet_hash_connect() to help the
> case where many attempts need to be made before finding
> an available 4-tuple.
>
> [...]
Here is the summary with links:
- [net-next,1/4] tcp: use RCU in __inet{6}_check_established()
https://git.kernel.org/netdev/net-next/c/ae9d5b19b322
- [net-next,2/4] tcp: optimize inet_use_bhash2_on_bind()
https://git.kernel.org/netdev/net-next/c/ca79d80b0b9f
- [net-next,3/4] tcp: add RCU management to inet_bind_bucket
https://git.kernel.org/netdev/net-next/c/d186f405fdf4
- [net-next,4/4] tcp: use RCU lookup in __inet_hash_connect()
https://git.kernel.org/netdev/net-next/c/86c2bc293b81
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-03-05 2:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 12:42 [PATCH net-next 0/4] tcp: scale connect() under pressure Eric Dumazet
2025-03-02 12:42 ` [PATCH net-next 1/4] tcp: use RCU in __inet{6}_check_established() Eric Dumazet
2025-03-03 0:24 ` Jason Xing
2025-03-04 0:20 ` Kuniyuki Iwashima
2025-03-02 12:42 ` [PATCH net-next 2/4] tcp: optimize inet_use_bhash2_on_bind() Eric Dumazet
2025-03-03 0:24 ` Jason Xing
2025-03-04 0:22 ` Kuniyuki Iwashima
2025-03-02 12:42 ` [PATCH net-next 3/4] tcp: add RCU management to inet_bind_bucket Eric Dumazet
2025-03-03 0:57 ` Jason Xing
2025-03-04 0:43 ` Kuniyuki Iwashima
2025-03-02 12:42 ` [PATCH net-next 4/4] tcp: use RCU lookup in __inet_hash_connect() Eric Dumazet
2025-03-03 1:07 ` Jason Xing
2025-03-03 10:25 ` Eric Dumazet
2025-03-03 10:39 ` Jason Xing
2025-03-04 0:51 ` Kuniyuki Iwashima
2025-03-10 14:03 ` kernel test robot
2025-03-05 2:00 ` 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=174114003473.368364.10864738728714771230.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=ncardwell@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).