diff --git a/doc/go1.21.html b/doc/go1.21.html index 075cee592acbf1..d3d79a2f258764 100644 --- a/doc/go1.21.html +++ b/doc/go1.21.html @@ -608,24 +608,33 @@
- TODO: https://go.dev/issue/56539: add support for MPTCP -
- -- TODO: https://go.dev/issue/59166: add func (*TCPConn) MultipathTCP() (bool, error) -
- -- TODO: https://go.dev/cl/471136: net: mptcp: implement dialMPTCP; modified api/next/56539.txt -
- -- TODO: https://go.dev/cl/471137: net: mptcp: implement listenMPTCP; modified api/next/56539.txt -
- -- TODO: https://go.dev/cl/471140: net: mptcp: add TCPConn's MultipathTCP checker; modified api/next/59166.txt +
+
+
+ On Linux, the net package can now use
+ Multipath TCP when the kernel supports it. It is not used by
+ default. To use Multipath TCP when available on a client, call
+ the
+ Dialer.SetMultipathTCP
+ method before calling the
+ Dialer.Dial
or
+ Dialer.DialContext
+ methods. To use Multipath TCP when available on a server, call
+ the
+ ListenConfig.SetMultipathTCP
+ method before calling the
+ ListenConfig.Listen
+ method. Specify the network as "tcp"
or
+ "tcp4"
or "tcp6"
as usual. If
+ Multipath TCP is not supported by the kernel or the remote host,
+ the connection will silently fall back to TCP. To test whether a
+ particular connection is using Multipath TCP, use the
+ TCPConn.MultipathTCP
+ method.
+
+ In a future Go release we may enable Multipath TCP by default on + systems that support it.