From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [RFC PATCH 0/4] mptcp: improve mptcp-level window tracking
Date: Mon, 11 Apr 2022 12:40:01 +0200 [thread overview]
Message-ID: <cover.1649672265.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).
With this series tput in the critical scenario raises from ~26 Gbps
(ranging in 4-30 Gbps) to ~43 Gbps (with min > 33 Gbps)
I guess patch 3/4 is the most debatable - expecially for RFC compliance
Any feedback more then welcome!
Note: still in patch 3/4, I'm unsure that the th->window update is
strictly necessary from functional perspective (e.g. possibly the atomic
operation is enough), I'll try to test that, too.
Paolo Abeni (4):
mptcp: really share subflow snd_wnd
mptcp: add mib for xmit window sharing
mptcp: never shrink offered window
mptcp: add more offered MIBs counter.
include/net/mptcp.h | 2 +-
net/ipv4/tcp_output.c | 2 +-
net/mptcp/mib.c | 4 +++
net/mptcp/mib.h | 6 +++++
net/mptcp/options.c | 61 +++++++++++++++++++++++++++++++++++++------
net/mptcp/protocol.c | 24 +++++++++++------
6 files changed, 81 insertions(+), 18 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-11 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 10:40 Paolo Abeni [this message]
2022-04-11 10:40 ` [RFC PATCH 1/4] mptcp: really share subflow snd_wnd Paolo Abeni
2022-04-11 10:40 ` [RFC PATCH 2/4] mptcp: add mib for xmit window sharing Paolo Abeni
2022-04-11 10:40 ` [RFC PATCH 3/4] mptcp: never shrink offered window Paolo Abeni
2022-04-11 18:23 ` kernel test robot
2022-04-11 19:46 ` kernel test robot
2022-04-15 0:39 ` Mat Martineau
2022-04-11 10:40 ` [RFC PATCH 4/4] mptcp: add more offered MIBs counter Paolo Abeni
2022-04-11 11:58 ` mptcp: add more offered MIBs counter.: Tests Results MPTCP CI
2022-04-11 13:49 ` [RFC PATCH 0/4] mptcp: improve mptcp-level window tracking Paolo Abeni
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.1649672265.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.