All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: dccp@vger.kernel.org
Subject: Re: [PATCH RESEND net-next v4 0/3] Add a second bind table hashed by port and address
Date: Thu, 25 Aug 2022 02:40:19 +0000	[thread overview]
Message-ID: <166139521930.434.1076457897005126686.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220822181023.3979645-1-joannelkoong@gmail.com>

Hello:

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

On Mon, 22 Aug 2022 11:10:20 -0700 you wrote:
> Currently, there is one bind hashtable (bhash) that hashes by port only.
> This patchset adds a second bind table (bhash2) that hashes by port and
> address.
> 
> The motivation for adding bhash2 is to expedite bind requests in situations
> where the port has many sockets in its bhash table entry (eg a large number
> of sockets bound to different addresses on the same port), which makes checking
> bind conflicts costly especially given that we acquire the table entry spinlock
> while doing so, which can cause softirq cpu lockups and can prevent new tcp
> connections.
> 
> [...]

Here is the summary with links:
  - [RESEND,net-next,v4,1/3] net: Add a bhash2 table hashed by port and address
    https://git.kernel.org/netdev/net-next/c/28044fc1d495
  - [RESEND,net-next,v4,2/3] selftests/net: Add test for timing a bind request to a port with a populated bhash entry
    https://git.kernel.org/netdev/net-next/c/c35ecb95c448
  - [RESEND,net-next,v4,3/3] selftests/net: Add sk_bind_sendto_listen and sk_connect_zero_addr
    https://git.kernel.org/netdev/net-next/c/1be9ac87a75a

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


WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Joanne Koong <joannelkoong@gmail.com>
Cc: netdev@vger.kernel.org, edumazet@google.com, kafai@fb.com,
	kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
	dccp@vger.kernel.org
Subject: Re: [PATCH RESEND net-next v4 0/3] Add a second bind table hashed by port and address
Date: Thu, 25 Aug 2022 02:40:19 +0000	[thread overview]
Message-ID: <166139521930.434.1076457897005126686.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220822181023.3979645-1-joannelkoong@gmail.com>

Hello:

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

On Mon, 22 Aug 2022 11:10:20 -0700 you wrote:
> Currently, there is one bind hashtable (bhash) that hashes by port only.
> This patchset adds a second bind table (bhash2) that hashes by port and
> address.
> 
> The motivation for adding bhash2 is to expedite bind requests in situations
> where the port has many sockets in its bhash table entry (eg a large number
> of sockets bound to different addresses on the same port), which makes checking
> bind conflicts costly especially given that we acquire the table entry spinlock
> while doing so, which can cause softirq cpu lockups and can prevent new tcp
> connections.
> 
> [...]

Here is the summary with links:
  - [RESEND,net-next,v4,1/3] net: Add a bhash2 table hashed by port and address
    https://git.kernel.org/netdev/net-next/c/28044fc1d495
  - [RESEND,net-next,v4,2/3] selftests/net: Add test for timing a bind request to a port with a populated bhash entry
    https://git.kernel.org/netdev/net-next/c/c35ecb95c448
  - [RESEND,net-next,v4,3/3] selftests/net: Add sk_bind_sendto_listen and sk_connect_zero_addr
    https://git.kernel.org/netdev/net-next/c/1be9ac87a75a

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



  reply	other threads:[~2022-08-25  2:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 18:10 [PATCH RESEND net-next v4 0/3] Add a second bind table hashed by port and address Joanne Koong
2022-08-22 18:10 ` Joanne Koong
2022-08-25  2:40 ` patchwork-bot+netdevbpf [this message]
2022-08-25  2:40   ` patchwork-bot+netdevbpf
  -- strict thread matches above, loose matches on Subject: below --
2022-08-22 18:10 [PATCH RESEND net-next v4 1/3] net: Add a bhash2 " Joanne Koong
2022-08-22 18:10 ` Joanne Koong
2022-08-22 18:10 [PATCH RESEND net-next v4 2/3] selftests/net: Add test for timing a bind request to a port with a po Joanne Koong
2022-08-22 18:10 ` [PATCH RESEND net-next v4 2/3] selftests/net: Add test for timing a bind request to a port with a populated bhash entry Joanne Koong
2022-08-22 18:10 [PATCH RESEND net-next v4 3/3] selftests/net: Add sk_bind_sendto_listen and sk_connect_zero_addr Joanne Koong
2022-08-22 18:10 ` Joanne Koong
2023-09-11 23:36 [PATCH RESEND net-next v4 1/3] net: Add a bhash2 table hashed by port and address Andrei Vagin
2023-09-11 23:36 ` Andrei Vagin
2023-09-12  0:06 ` Iwashima, Kuniyuki
2023-09-12  0:06   ` Iwashima, Kuniyuki

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=166139521930.434.1076457897005126686.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dccp@vger.kernel.org \
    /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.