From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH net-next 0/5] mptcp: improve mptcp-level window tracking
Date: Fri, 15 Apr 2022 16:48:43 +0200 [thread overview]
Message-ID: <cover.1650034062.git.pabeni@redhat.com> (raw)
I've been chasing bad/unstable performances 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
- 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 3/4.
- 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
This series additionally bump 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 su much
noticeable, still in the current setup the tput changes from
[6-18] Gbps to 19Gbps very stable.
RFC -> v1:
- added patch 3/5 to address Mat's comment, and rebased the
following on top of it - I hope Eric may tolerate that, it's
more an hope than guess ;)
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 | 13 +++++-----
net/mptcp/mib.c | 4 +++
net/mptcp/mib.h | 6 +++++
net/mptcp/options.c | 58 +++++++++++++++++++++++++++++++++++++------
net/mptcp/protocol.c | 24 ++++++++++++------
6 files changed, 84 insertions(+), 23 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-15 14:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 14:48 Paolo Abeni [this message]
2022-04-15 14:48 ` [PATCH net-next 1/5] mptcp: really share subflow snd_wnd Paolo Abeni
2022-04-15 14:48 ` [PATCH net-next 2/5] mptcp: add mib for xmit window sharing Paolo Abeni
2022-04-15 14:48 ` [PATCH net-next 3/5] tcp: allow MPTCP to update the announced window Paolo Abeni
2022-04-19 0:11 ` Mat Martineau
2022-04-19 10:42 ` Paolo Abeni
2022-04-20 16:18 ` Paolo Abeni
2022-04-15 14:48 ` [PATCH net-next 4/5] mptcp: never shrink offered window Paolo Abeni
2022-04-19 0:29 ` Mat Martineau
2022-04-19 10:40 ` Paolo Abeni
2022-04-15 14:48 ` [PATCH net-next 5/5] mptcp: add more offered MIBs counter Paolo Abeni
2022-04-15 15:10 ` mptcp: add more offered MIBs counter.: Build Failure MPTCP CI
2022-04-15 16:39 ` Matthieu Baerts
2022-04-15 16:54 ` mptcp: add more offered MIBs counter.: Tests Results MPTCP CI
-- strict thread matches above, loose matches on Subject: below --
2022-05-04 21:54 [PATCH net-next 0/5] mptcp: Improve MPTCP-level window tracking Mat Martineau
2022-05-04 22:05 ` Mat Martineau
2022-05-06 2:20 ` 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=cover.1650034062.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox