From: Matthieu Baerts <matttbe@kernel.org>
To: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v7 3/6] mptcp: pm: in-kernel: add the subflow-retries limit
Date: Thu, 22 Oct 2026 12:19:39 +0200 [thread overview]
Message-ID: <56679372-0ae6-43bf-b0fa-a6b853a1b68c@kernel.org> (raw)
In-Reply-To: <20261020031711.1896660-4-anilkaushikwireless@gmail.com>
On 20/10/2026 05:17, Anil Kaushik wrote:
> A new limit for the in-kernel PM, set and read with the other limits:
> the number of SYN retries of a subflow re-created after an error, like
> the TCP_SYNCNT socket option. 15 by default, about 20 minutes, and 0
> to not re-create it. The netlink policy checks the maximum value,
> MAX_TCP_SYNCNT.
>
> It is also exposed in struct mptcp_info, in place of the reserved field.
>
> The next patch uses it.
>
> Assisted-by: LLM
> Signed-off-by: Anil Kaushik <anilkaushikwireless@gmail.com>
> ---
>
> Notes:
> v6:
> - the netlink policy checks the maximum, no more parse_limit() change
> (netdev Sashiko)
> - the limit works like TCP_SYNCNT, say so (netdev Sashiko)
That's a good idea to use netlink policy to check the maximum. Do you
mind adding a patch between the current 1 and 2 to do the same with the
other 2 limits to uniform everything, please?
Either that, or continuing to use parse_limit(), but better not to have
a mix of the two.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-10-22 10:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 3:17 [PATCH mptcp-next v7 0/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
2026-10-20 3:17 ` [PATCH mptcp-next v7 1/6] selftests: mptcp: connect: retry write() on EAGAIN Anil Kaushik
2026-10-20 3:17 ` [PATCH mptcp-next v7 2/6] netlink: specs: mptcp: add the subflow-retries attribute Anil Kaushik
2026-10-20 3:17 ` [PATCH mptcp-next v7 3/6] mptcp: pm: in-kernel: add the subflow-retries limit Anil Kaushik
2026-10-22 10:19 ` Matthieu Baerts [this message]
2026-10-20 3:17 ` [PATCH mptcp-next v7 4/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
2026-10-20 8:37 ` sashiko-bot
2026-10-21 16:36 ` netdev-bot+sashiko
2026-10-20 3:17 ` [PATCH mptcp-next v7 5/6] selftests: mptcp: pm_nl_ctl: support the subflow-retries limit Anil Kaushik
2026-10-20 3:17 ` [PATCH mptcp-next v7 6/6] selftests: mptcp: join: validate subflow retry after link failure Anil Kaushik
2026-10-21 16:36 ` netdev-bot+sashiko
2026-10-21 12:44 ` [PATCH mptcp-next v7 0/6] mptcp: pm: in-kernel: retry subflows closed after an error MPTCP CI
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=56679372-0ae6-43bf-b0fa-a6b853a1b68c@kernel.org \
--to=matttbe@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 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.