From: Dmytro Shytyi <dmytro@shytyi.net>
To: mptcp@lists.linux.dev
Cc: Dmytro Shytyi <dmytro@shytyi.net>
Subject: [RFC PATCH mptcp-next v13 6/7] mptcp: add TCP_FASTOPEN sock option
Date: Sat, 1 Oct 2022 03:15:01 +0000 [thread overview]
Message-ID: <20221001031502.29152-7-dmytro@shytyi.net> (raw)
In-Reply-To: <20221001031502.29152-1-dmytro@shytyi.net>
We add the TCP_FASTOPEN socket option in this patch that is going to
be set by the listener side.
Signed-off-by: Dmytro Shytyi <dmytro@shytyi.net>
---
net/mptcp/sockopt.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/net/mptcp/sockopt.c b/net/mptcp/sockopt.c
index f85e9bbfe86f..7f6977295256 100644
--- a/net/mptcp/sockopt.c
+++ b/net/mptcp/sockopt.c
@@ -559,6 +559,7 @@ static bool mptcp_supported_sockopt(int level, int optname)
case TCP_NOTSENT_LOWAT:
case TCP_TX_DELAY:
case TCP_INQ:
+ case TCP_FASTOPEN:
case TCP_FASTOPEN_CONNECT:
case TCP_FASTOPEN_NO_COOKIE:
return true;
@@ -569,7 +570,7 @@ static bool mptcp_supported_sockopt(int level, int optname)
/* TCP_REPAIR, TCP_REPAIR_QUEUE, TCP_QUEUE_SEQ, TCP_REPAIR_OPTIONS,
* TCP_REPAIR_WINDOW are not supported, better avoid this mess
*/
- /* TCP_FASTOPEN_KEY, TCP_FASTOPEN are not supported because
+ /* TCP_FASTOPEN_KEY is not supported because
* fastopen for the listener side is currently unsupported
*/
}
@@ -801,6 +802,7 @@ static int mptcp_setsockopt_sol_tcp(struct mptcp_sock *msk, int optname,
/* See tcp.c: TCP_DEFER_ACCEPT does not fail */
mptcp_setsockopt_first_sf_only(msk, SOL_TCP, optname, optval, optlen);
return 0;
+ case TCP_FASTOPEN:
case TCP_FASTOPEN_CONNECT:
case TCP_FASTOPEN_NO_COOKIE:
return mptcp_setsockopt_first_sf_only(msk, SOL_TCP, optname,
@@ -1166,6 +1168,7 @@ static int mptcp_getsockopt_sol_tcp(struct mptcp_sock *msk, int optname,
case TCP_INFO:
case TCP_CC_INFO:
case TCP_DEFER_ACCEPT:
+ case TCP_FASTOPEN:
case TCP_FASTOPEN_CONNECT:
case TCP_FASTOPEN_NO_COOKIE:
return mptcp_getsockopt_first_sf_only(msk, SOL_TCP, optname,
--
2.34.1
next prev parent reply other threads:[~2022-10-01 3:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 3:14 [RFC PATCH mptcp-next v13 0/7] mptcp: Fast Open Mechanism Dmytro Shytyi
2022-10-01 3:14 ` [RFC PATCH mptcp-next v13 1/7] mptcp: add __mptcp_pre_connect() helper Dmytro Shytyi
2022-10-01 3:14 ` [RFC PATCH mptcp-next v13 2/7] mptcp: add __mptcp_stream_connect() helper Dmytro Shytyi
2022-10-01 3:14 ` [RFC PATCH mptcp-next v13 3/7] mptcp: introduce MSG_FASTOPEN flag Dmytro Shytyi
2022-10-01 3:14 ` [RFC PATCH mptcp-next v13 4/7] mptcp: implement delayed seq generation for passive fastopen Dmytro Shytyi
2022-10-01 3:15 ` [RFC PATCH mptcp-next v13 5/7] mptcp: add subflow_v(4,6)_send_synack() Dmytro Shytyi
2022-10-01 3:15 ` Dmytro Shytyi [this message]
2022-10-01 3:15 ` [RFC PATCH mptcp-next v13 7/7] selftests: mptfo initiator/listener Dmytro Shytyi
2022-10-06 12:51 ` selftests: mptfo initiator/listener: Build Failure MPTCP CI
2022-10-06 15:16 ` selftests: mptfo initiator/listener: Tests Results MPTCP CI
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=20221001031502.29152-7-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).