diff options
| author | Aperence <anthony.doeraene@hotmail.com> | 2024-08-28 17:45:58 +0000 |
|---|---|---|
| committer | Gopher Robot <gobot@golang.org> | 2024-09-03 15:27:29 +0000 |
| commit | 3d4daa38a763260e07f4745110f2b5fcbec25126 (patch) | |
| tree | 0dc1e950d787ee2b68916b6ad8a6aa57fa68d7d1 /doc/godebug.md | |
| parent | a9e6a96ac092cc5191d759488ee761e9a403ab8f (diff) | |
| download | go-3d4daa38a763260e07f4745110f2b5fcbec25126.tar.xz | |
net: enable multipath TCP by default for listeners
A previous change [1] was introduced to enable MPTCP by default
for both the clients and servers, based on the discussions [2] in
golang#56539, where MPTCP would be an opt-in for a release or
two, and then would become an opt-out.
This change was not accepted at the time because the support for
a few socket options was missing [3]. Now that this support has been
added [4] and backported to stable versions not to block MPTCP
deployment with Go, it sounds like a good time to reconsider the use
of MPTCP by default.
Instead of enabling MPTCP on both ends by default, as a first step,
it seems safer to change the default behaviour only for the server
side (Listeners). On the server side, the impact is minimal: when
clients don't request to use MPTCP, server applications will create
"plain" TCP sockets within the kernel when connections are accepted,
making the performance impact minimal. This should also ease
experiments where MPTCP is enabled by default on the client side
(Dialer).
The changes in this patch consist of a duplication of the mptcpStatus
enumeration to have both a mptcpStatusDial and a mptcpStatusListen,
where MPTCP is enabled by default in mptcpStatusListen, but disabled
by default in mptcpStatusDial. It is still possible to turn MPTCP support
on and off by using GODEBUG=multipathtcp=1.
[1] https://go-review.googlesource.com/c/go/+/563575
[2] https://go.dev/issue/56539#issuecomment-1309294637
[3] https://github.com/multipath-tcp/mptcp_net-next/issues/383
[4] https://github.com/torvalds/linux/commit/bd11dc4fb969ec148e50cd87f88a78246dbc4d0b
[5] https://www.mptcp.dev/faq.html#why--when-should-mptcp-be-enabled-by-default
Updates #56539
Change-Id: I1ca0d6aaf74d3bda5468af135e29cdb405d3fd00
GitHub-Last-Rev: 5f9f29bfc13ad4ea6bfd1e0fc95a91bd824f4048
GitHub-Pull-Request: golang/go#69016
Reviewed-on: https://go-review.googlesource.com/c/go/+/607715
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Reviewed-by: Matthieu Baerts <matttbe@kernel.org>
Auto-Submit: Ian Lance Taylor <iant@google.com>
Diffstat (limited to 'doc/godebug.md')
| -rw-r--r-- | doc/godebug.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/godebug.md b/doc/godebug.md index 51ec4cb05a..7b5fd3e48b 100644 --- a/doc/godebug.md +++ b/doc/godebug.md @@ -157,6 +157,17 @@ no-op. This behavior is controlled by the `randseednop` setting. For Go 1.24 it defaults to `randseednop=1`. Using `randseednop=0` reverts to the pre-Go 1.24 behavior. +Go 1.24 added new values for the `multipathtcp` setting. +The possible values for `multipathtcp` are now: +- "0": disable MPTCP on dialers and listeners by default +- "1": enable MPTCP on dialers and listeners by default +- "2": enable MPTCP on listeners only by default +- "3": enable MPTCP on dialers only by default + +For Go 1.24, it now defaults to multipathtcp="2", thus +enabled by default on listerners. Using multipathtcp="0" reverts to the +pre-Go 1.24 behavior. + ### Go 1.23 Go 1.23 changed the channels created by package time to be unbuffered |