diff options
| author | Matthieu Baerts (NGI0) <matttbe@kernel.org> | 2026-05-08 17:40:49 +0200 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-05-11 18:01:37 -0700 |
| commit | e845e6397d78bf6b842cfa8b5818ca8189f7e22e (patch) | |
| tree | f8e91dee671da9bdc57d77e2c2b6187505791bd7 /scripts/stackusage | |
| parent | 607f16ab462beaa4e84a3ce00a80c91e00d28a41 (diff) | |
mptcp: pm: in-kernel: increase endpoints limit
The endpoints are managed in a list which was limited to 8 entries.
This limit can be too small in some cases: by having the same limit as
the number of subflows, it might not allow creating all expected
subflows when having a mix of v4 and v6 addresses that can all use MPTCP
on v4/v6 only networks.
While increasing the limit above the new subflows one, why not using the
technical limit: 255. Indeed, the endpoint will each have an ID that
will be used on the wire, limited to u8, and the ID 0 is reserved to the
initial subflow.
Reviewed-by: Mat Martineau <martineau@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Link: https://patch.msgid.link/20260508-net-next-mptcp-pm-inc-limits-v1-4-c84e3fdf9b6a@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions
