Allow switching from 8 to 64 for the maximum number of subflows and
accepted ADD_ADDR, and from 8 to 255 for the number of MPTCP endpoints.

The previous limit of 8 subflows makes sense in most cases. Using more
subflows will very likely *not* improve the situation, and could even
decrease the performances. But there are no technical limitations nor
performance impact to raise this limit, so let's do it: this will allow
people with very specific use-cases, and researchers to easily create
more subflows, and measure the performance impact by themselves.

- Patches 1-2: increase subflows and accepted ADD_ADDR limits.

- Patches 3-4: increase endpoints limit.

- Patches 5-7: validate the new limits: 64 subflows, 255 endpoints.

- Patch 8: selftests: use send()/recv() instead of sendto()/recvfrom().

Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Matthieu Baerts (NGI0) (8):
      mptcp: pm: in-kernel: explicitly limit batches to array size
      mptcp: pm: in-kernel: increase all limits to 64
      mptcp: pm: kernel: allow flushing more than 8 endpoints
      mptcp: pm: in-kernel: increase endpoints limit
      selftests: mptcp: join: allow changing ifaces nr per test
      selftests: mptcp: join: validate 8x8 subflows
      selftests: mptcp: pm: validate new limits
      selftests: mptcp: pm: use simpler send/recv forms

 net/mptcp/pm_kernel.c                           | 77 +++++++++++++++++--------
 tools/testing/selftests/net/mptcp/mptcp_join.sh | 33 ++++++++++-
 tools/testing/selftests/net/mptcp/pm_netlink.sh | 56 +++++++++++-------
 tools/testing/selftests/net/mptcp/pm_nl_ctl.c   |  8 +--
 4 files changed, 121 insertions(+), 53 deletions(-)
---
base-commit: 6a4c4656b0d2d4056a1f0c35442db4e8a5cf8021
change-id: 20260508-net-next-mptcp-pm-inc-limits-b825af50e400

Best regards,
--  
Matthieu Baerts (NGI0) <matttbe@kernel.org>

Hello:

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

On Fri, 08 May 2026 17:40:45 +0200 you wrote:
> Allow switching from 8 to 64 for the maximum number of subflows and
> accepted ADD_ADDR, and from 8 to 255 for the number of MPTCP endpoints.
> 
> The previous limit of 8 subflows makes sense in most cases. Using more
> subflows will very likely *not* improve the situation, and could even
> decrease the performances. But there are no technical limitations nor
> performance impact to raise this limit, so let's do it: this will allow
> people with very specific use-cases, and researchers to easily create
> more subflows, and measure the performance impact by themselves.
> 
> [...]

Here is the summary with links:
  - [net-next,1/8] mptcp: pm: in-kernel: explicitly limit batches to array size
    https://git.kernel.org/netdev/net-next/c/9031e5e31d5d
  - [net-next,2/8] mptcp: pm: in-kernel: increase all limits to 64
    https://git.kernel.org/netdev/net-next/c/c8646664fbf1
  - [net-next,3/8] mptcp: pm: kernel: allow flushing more than 8 endpoints
    https://git.kernel.org/netdev/net-next/c/607f16ab462b
  - [net-next,4/8] mptcp: pm: in-kernel: increase endpoints limit
    https://git.kernel.org/netdev/net-next/c/e845e6397d78
  - [net-next,5/8] selftests: mptcp: join: allow changing ifaces nr per test
    https://git.kernel.org/netdev/net-next/c/e1515a1a494b
  - [net-next,6/8] selftests: mptcp: join: validate 8x8 subflows
    https://git.kernel.org/netdev/net-next/c/1697837a67fa
  - [net-next,7/8] selftests: mptcp: pm: validate new limits
    https://git.kernel.org/netdev/net-next/c/c9b581e619d2
  - [net-next,8/8] selftests: mptcp: pm: use simpler send/recv forms
    https://git.kernel.org/netdev/net-next/c/ed5372634c5b

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