From: Matthieu Baerts <matttbe@kernel.org>
To: Mat Martineau <martineau@kernel.org>
Cc: MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-net v6 00/19] mptcp: pm: increase limits, and related fixes and cleanup
Date: Wed, 29 Apr 2026 09:39:06 +0200 [thread overview]
Message-ID: <cd32f04b-0ebe-4075-852b-b4ebe083d9c3@kernel.org> (raw)
In-Reply-To: <8a91a5e4-1fa2-6c06-8cc4-89a4f3d87d36@kernel.org>
Hi Mat,
On 29/04/2026 02:09, Mat Martineau wrote:
> On Wed, 22 Apr 2026, Matthieu Baerts (NGI0) wrote:
>
>> The initial intension was to increase the limits, but some fixes were
>> needed, then when looking at the code around, other fixes had to be
>> added too. So now I ended up with multiple fixes (including one early
>> exit while at it), followed by patches increasing limits with some
>> adaptations required before, some to validate the modifications, and one
>> small improvement in the selftests.
>>
>> The patches with a Fixes tag are for -net, the rest for net-next.
>>
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>> ---
>> Changes in v6:
>> - patch 4: fix label name in commit message + mention next patch.
>> - patch 7: use min() to improve clarity (Mat)
>> - patch 15: fix typo.
>> - patch 20: removed: will be sent in another series after that one.
>> - Link to v5: https://patch.msgid.link/20260415-mptcp-inc-limits-v5-0-
>> e54c3bf80e4e@kernel.org
>
> Hi Matthieu -
>
> v6 LGTM, thanks for the updates.
Thank you for the review!
Now in our tree:
New patches for t/upstream-net and t/upstream:
- 4cd1d0bb0a77: mptcp: pm: kernel: correctly retransmit ADD_ADDR ID 0
- 24d6e9230abb: mptcp: pm: ADD_ADDR rtx: fix potential data-race
- 1d62197aebe7: mptcp: pm: ADD_ADDR rtx: allow ID 0
- 3e8311058b8a: mptcp: pm: ADD_ADDR rtx: always decrease sk refcount
- c7492016b448: mptcp: pm: ADD_ADDR rtx: free sk if last
- 999a20ff8f59: mptcp: pm: ADD_ADDR rtx: resched blocked ADD_ADDR quicker
- 20269ec49bd8: mptcp: pm: ADD_ADDR rtx: skip inactive subflows
- a91b0640998b: mptcp: pm: ADD_ADDR rtx: return early if no retrans
- 09b51d25b19b: mptcp: pm: prio: skip closed subflows
- 53421f820dd0: selftests: mptcp: check output: catch cmd errors
- f1dcf11f1a08: selftests: mptcp: pm: restrict 'unknown' check to pm_nl_ctl
- Results: 90cb02b20cf2..2a1f2d9ea26c (export-net)
- Results: f68dc562c883..eff6f637e315 (export)
New patches for t/upstream:
- 43bbf39ee203: mptcp: pm: in-kernel: explicitly limit batches to array size
- aec0321c2d29: mptcp: pm: in-kernel: increase all limits to 64
- a6d8f6739145: mptcp: pm: kernel: allow flushing more than 8 endpoints
- db7b26d14b03: mptcp: pm: in-kernel: increase endpoints limit
- 4097388c8d85: selftests: mptcp: join: allow changing ifaces nr per test
- b72b1d12a597: selftests: mptcp: join: validate 8x8 subflows
- 67c280697ab2: selftests: mptcp: pm: validate new limits
- dade65b5a91d: selftests: mptcp: pm: use simpler send/recv forms
- Results: eff6f637e315..d56fb1eba9f2 (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/6f73a831d415e285b7e49565b9079495b7274a89/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/ea2792a55b2660faf08c4a65ad46d7b87adf6f1c/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-04-29 7:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 16:40 [PATCH mptcp-net v6 00/19] mptcp: pm: increase limits, and related fixes and cleanup Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 01/19] mptcp: pm: kernel: correctly retransmit ADD_ADDR ID 0 Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 02/19] mptcp: pm: ADD_ADDR rtx: fix potential data-race Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 03/19] mptcp: pm: ADD_ADDR rtx: allow ID 0 Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 04/19] mptcp: pm: ADD_ADDR rtx: always decrease sk refcount Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 05/19] mptcp: pm: ADD_ADDR rtx: free sk if last Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 06/19] mptcp: pm: ADD_ADDR rtx: resched blocked ADD_ADDR quicker Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 07/19] mptcp: pm: ADD_ADDR rtx: skip inactive subflows Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 08/19] mptcp: pm: retrans ADD_ADDR: return early if no retrans Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 09/19] mptcp: pm: prio: skip closed subflows Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 10/19] selftests: mptcp: check output: catch cmd errors Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 11/19] selftests: mptcp: pm: restrict 'unknown' check to pm_nl_ctl Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 12/19] mptcp: pm: in-kernel: explicitly limit batches to array size Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 13/19] mptcp: pm: in-kernel: increase all limits to 64 Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 14/19] mptcp: pm: kernel: allow flushing more than 8 endpoints Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 15/19] mptcp: pm: in-kernel: increase endpoints limit Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 16/19] selftests: mptcp: join: allow changing ifaces nr per test Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 17/19] selftests: mptcp: join: validate 8x8 subflows Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 18/19] selftests: mptcp: pm: validate new limits Matthieu Baerts (NGI0)
2026-04-22 16:40 ` [PATCH mptcp-net v6 19/19] selftests: mptcp: pm: use simpler send/recv forms Matthieu Baerts (NGI0)
2026-04-22 17:47 ` [PATCH mptcp-net v6 00/19] mptcp: pm: increase limits, and related fixes and cleanup MPTCP CI
2026-04-29 0:09 ` Mat Martineau
2026-04-29 7:39 ` Matthieu Baerts [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=cd32f04b-0ebe-4075-852b-b4ebe083d9c3@kernel.org \
--to=matttbe@kernel.org \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
/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