From: Dmytro Shytyi <dmytro@shytyi.net>
To: mptcp@lists.linux.dev
Cc: Dmytro Shytyi <dmytro@shytyi.net>
Subject: [RFC PATCH mptcp-next v9 0/6] mptcp: Fast Open Mechanism
Date: Wed, 21 Sep 2022 14:55:52 +0200 [thread overview]
Message-ID: <20220921125558.19483-1-dmytro@shytyi.net> (raw)
[PATCH v9] includes "client-server" partial support for:
1. MPTCP cookie request from client (seems OK).
2. MPTCP cookie offering from server (seems OK).
3. MPTCP SYN+DATA+COOKIE from client (seems OK).
4. subsequent write + read on the opened socket (seems OK).
===Changes between v8 and v9
- Code is refactored (Max. reuse of existing linux kernel code).
- impact on fastopen.c is reduced to minima due to added function
subflow_v4_send_synack().
===Future work
-Adress the appearance of "MPTCP FIN" as duplicated acks.
-Integrate presented in the last patch selftests.
Dmytro Shytyi (6):
mptcp: add mptcp_stream_connect to protocol.h
mptcp: add mptcp_setsockopt_fastopen
mptcp: reuse tcp_sendmsg_fastopen()
mptcp: fix retrans., add mptfo vars to msk
mptcp: add subflow_v(4,6)_send_synack()
selftests: mptfo initiator/listener
include/net/tcp.h | 3 +
net/ipv4/tcp.c | 24 ++++-
net/ipv4/tcp_fastopen.c | 19 ++--
net/mptcp/Makefile | 2 +-
net/mptcp/fastopen.c | 46 ++++++++
net/mptcp/options.c | 5 +
net/mptcp/protocol.c | 35 +++++-
net/mptcp/protocol.h | 10 ++
net/mptcp/sockopt.c | 3 +
net/mptcp/subflow.c | 70 ++++++++++++
tools/testing/selftests/net/mptcp/mptfo.sh | 13 +++
.../selftests/net/mptcp/mptfo_initiator.c | 43 ++++++++
.../selftests/net/mptcp/mptfo_listener.c | 100 ++++++++++++++++++
13 files changed, 356 insertions(+), 17 deletions(-)
create mode 100644 net/mptcp/fastopen.c
create mode 100644 tools/testing/selftests/net/mptcp/mptfo.sh
create mode 100644 tools/testing/selftests/net/mptcp/mptfo_initiator.c
create mode 100644 tools/testing/selftests/net/mptcp/mptfo_listener.c
--
2.25.1
next reply other threads:[~2022-09-21 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 12:55 Dmytro Shytyi [this message]
2022-09-21 12:55 ` [RFC PATCH mptcp-next v9 1/6] mptcp: add mptcp_stream_connect to protocol.h Dmytro Shytyi
2022-09-21 12:55 ` [RFC PATCH mptcp-next v9 2/6] mptcp: add mptcp_setsockopt_fastopen Dmytro Shytyi
2022-09-21 12:55 ` [RFC PATCH mptcp-next v9 3/6] mptcp: reuse tcp_sendmsg_fastopen() Dmytro Shytyi
2022-09-21 12:55 ` [RFC PATCH mptcp-next v9 4/6] mptcp: fix retrans., add mptfo vars to msk Dmytro Shytyi
2022-09-21 18:02 ` Paolo Abeni
2022-09-22 11:53 ` Dmytro Shytyi
2022-09-21 12:55 ` [RFC PATCH mptcp-next v9 5/6] mptcp: add subflow_v(4,6)_send_synack() Dmytro Shytyi
2022-09-21 18:00 ` Paolo Abeni
2022-09-22 11:50 ` Dmytro Shytyi
2022-09-21 12:55 ` [RFC PATCH mptcp-next v9 6/6] selftests: mptfo initiator/listener Dmytro Shytyi
2022-09-21 13:38 ` selftests: mptfo initiator/listener: Build Failure MPTCP CI
2022-09-21 15:01 ` selftests: mptfo initiator/listener: Tests Results MPTCP CI
2022-09-22 23:23 ` [PATCH mptcp-next v2 0/4] mptcp: add support for TFO, sender side only Dmytro Shytyi
2022-09-23 10:58 ` Matthieu Baerts
2022-09-23 13:41 ` Dmytro Shytyi
2022-09-23 14:08 ` Matthieu Baerts
2022-09-23 14:17 ` Dmytro Shytyi
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=20220921125558.19483-1-dmytro@shytyi.net \
--to=dmytro@shytyi.net \
--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;
as well as URLs for NNTP newsgroup(s).