From: Matthieu Baerts <matttbe@kernel.org>
To: Gang Yan <gang.yan@linux.dev>, MPTCP Linux <mptcp@lists.linux.dev>
Cc: Gang Yan <yangang@kylinos.cn>
Subject: Re: [PATCH mptcp-net v3] mptcp: update window_clamp on subflows when SO_RCVBUF is set
Date: Fri, 8 May 2026 12:54:50 +0200 [thread overview]
Message-ID: <ef8a156b-e0ce-4ecc-8b40-9b826eea897f@kernel.org> (raw)
In-Reply-To: <20260506-window_clamp-v3-1-ade82fbbebb2@kylinos.cn>
Hi Gang,
On 06/05/2026 11:43, Gang Yan wrote:
> From: Gang Yan <yangang@kylinos.cn>
>
> Add __mptcp_subflow_set_rcvbuf() helper that calls the tcp_set_rcvbuf
> to update window_clamp, in addition to writing sk_rcvbuf. Use it in
> both mptcp_sol_socket_sync_intval() (setsockopt path) and
> sync_socket_options() (new subflow creation path).
Now in our tree, with small modifications in the commit message.
New patches for t/upstream-net and t/upstream:
- 840fb208ba03: mptcp: update window_clamp on subflows when SO_RCVBUF is set
- Results: 83b57683234a..a968ca54c292 (export-net)
- Results: fac20e19a7d2..9ec315f69069 (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/ebbd36260bf0fc51690fbf16c146a51f95d32602/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/876e5cac2c615fa953d03f4b90ab234ebfca3c73/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-05-08 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 9:43 [PATCH mptcp-net v3] mptcp: update window_clamp on subflows when SO_RCVBUF is set Gang Yan
2026-05-06 11:19 ` MPTCP CI
2026-05-08 9:24 ` Matthieu Baerts
2026-05-08 10:54 ` 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=ef8a156b-e0ce-4ecc-8b40-9b826eea897f@kernel.org \
--to=matttbe@kernel.org \
--cc=gang.yan@linux.dev \
--cc=mptcp@lists.linux.dev \
--cc=yangang@kylinos.cn \
/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