From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: Eric Dumazet <eric.dumazet@gmail.com>, mptcp@lists.linux.dev
Subject: [RFC PATCH 0/2] mptcp: never shrink offered window
Date: Tue, 19 Apr 2022 19:18:22 +0200 [thread overview]
Message-ID: <cover.1650386197.git.pabeni@redhat.com> (raw)
There patches are part of a somewhat largish series to implement
more strict RFC compliance for the MPTCP-level congestion window
handling, solving some tput instability issues.
The obtain the above we need to modify an existing MPTCP hook,
touching the TCP code (in patch 1/2), ence the RFC.
The later patch demonstrates the actual usage of such hook.
Paolo Abeni (2):
tcp: allow MPTCP to update the announced window.
mptcp: never shrink offered window
include/net/mptcp.h | 2 +-
net/ipv4/tcp_output.c | 14 ++++++-----
net/mptcp/options.c | 54 ++++++++++++++++++++++++++++++++++++-------
3 files changed, 55 insertions(+), 15 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-19 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 17:18 Paolo Abeni [this message]
2022-04-19 17:18 ` [RFC PATCH 1/2] tcp: allow MPTCP to update the announced window Paolo Abeni
2022-04-19 17:18 ` [RFC PATCH 2/2] mptcp: never shrink offered window 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.1650386197.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/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).