[PATCH net-next 0/8] mptcp: pm: in-kernel: increase limits

[Matthieu Baerts (NGI0)]

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@xxxxxxxxxx>
---
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@xxxxxxxxxx>