From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, matthieu.baerts@tessares.net,
mptcp@lists.linux.dev
Subject: Re: [PATCH net-next 0/5] mptcp: Improve MPTCP-level window tracking
Date: Wed, 4 May 2022 15:05:45 -0700 (PDT) [thread overview]
Message-ID: <73fb3f63-c10-2c9c-91a0-3567a838512@linux.intel.com> (raw)
In-Reply-To: <20220504215408.349318-1-mathew.j.martineau@linux.intel.com>
On Wed, 4 May 2022, Mat Martineau wrote:
> This series improves MPTCP receive window compliance with RFC 8684 and
> helps increase throughput on high-speed links. Note that patch 3 makes a
> change in tcp_output.c
>
> For the details, Paolo says:
>
> I've been chasing bad/unstable performance with multiple subflows
> on very high speed links.
>
> It looks like the root cause is due to the current mptcp-level
> congestion window handling. There are apparently a few different
> sub-issues:
>
> - the rcv_wnd is not effectively shared on the tx side, as each
> subflow takes in account only the value received by the underlaying
> TCP connection. This is addressed in patch 1/4
I missed a couple of small edits - this should be "patch 1/5"...
>
> - The mptcp-level offered wnd right edge is currently allowed to shrink.
> Reading section 3.3.4.:
>
> """
> The receive window is relative to the DATA_ACK. As in TCP, a
> receiver MUST NOT shrink the right edge of the receive window (i.e.,
> DATA_ACK + receive window). The receiver will use the data sequence
> number to tell if a packet should be accepted at the connection
> level.
> """
>
> I read the above as we need to reflect window right-edge tracking
> on the wire, see patch 4/5.
>
> - The offered window right edge tracking can happen concurrently on
> multiple subflows, but there is no mutex protection. We need an
> additional atomic operation - still patch 3/4
...and this "patch 4/5".
- Mat
>
> This series additionally bumps a few new MIBs to track all the above
> (ensure/observe that the suspected races actually take place).
>
> I could not access again the host where the issue was so
> noticeable, still in the current setup the tput changes from
> [6-18] Gbps to 19Gbps very stable.
>
>
> Paolo Abeni (5):
> mptcp: really share subflow snd_wnd
> mptcp: add mib for xmit window sharing
> tcp: allow MPTCP to update the announced window
> mptcp: never shrink offered window
> mptcp: add more offered MIBs counter
>
> include/net/mptcp.h | 2 +-
> net/ipv4/tcp_output.c | 14 ++++++-----
> net/mptcp/mib.c | 4 +++
> net/mptcp/mib.h | 6 +++++
> net/mptcp/options.c | 58 +++++++++++++++++++++++++++++++++++++------
> net/mptcp/protocol.c | 32 +++++++++++++++---------
> net/mptcp/protocol.h | 2 +-
> 7 files changed, 90 insertions(+), 28 deletions(-)
>
>
> base-commit: a37f37a2e7f5ea3ae2a1278f552aa21a8e32c221
> --
> 2.36.0
>
>
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-05-04 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 21:54 [PATCH net-next 0/5] mptcp: Improve MPTCP-level window tracking Mat Martineau
2022-05-04 21:54 ` [PATCH net-next 1/5] mptcp: really share subflow snd_wnd Mat Martineau
2022-05-04 21:54 ` [PATCH net-next 2/5] mptcp: add mib for xmit window sharing Mat Martineau
2022-05-04 21:54 ` [PATCH net-next 3/5] tcp: allow MPTCP to update the announced window Mat Martineau
2022-05-04 21:54 ` [PATCH net-next 4/5] mptcp: never shrink offered window Mat Martineau
2022-05-04 21:54 ` [PATCH net-next 5/5] mptcp: add more offered MIBs counter Mat Martineau
2022-05-04 22:05 ` Mat Martineau [this message]
2022-05-06 2:20 ` [PATCH net-next 0/5] mptcp: Improve MPTCP-level window tracking patchwork-bot+netdevbpf
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=73fb3f63-c10-2c9c-91a0-3567a838512@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).