From: Yumei Huang <yuhuang@redhat.com>
To: passt-dev@passt.top, sbrivio@redhat.com
Cc: david@gibson.dropbear.id.au, yuhuang@redhat.com
Subject: [PATCH v9 4/5] tcp: Update data retransmission timeout
Date: Tue, 25 Nov 2025 15:26:37 +0800 [thread overview]
Message-ID: <20251125072638.88896-5-yuhuang@redhat.com> (raw)
In-Reply-To: <20251125072638.88896-1-yuhuang@redhat.com>
Use an exponential backoff timeout for data retransmission according
to RFC 2988 and RFC 6298. Set the initial RTO to one second as discussed
in Appendix A of RFC 6298.
Also combine the macros defining the initial RTO for both SYN and ACK.
Signed-off-by: Yumei Huang <yuhuang@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
---
tcp.c | 31 ++++++++++++-------------------
1 file changed, 12 insertions(+), 19 deletions(-)
diff --git a/tcp.c b/tcp.c
index 2887f2c..b3aa064 100644
--- a/tcp.c
+++ b/tcp.c
@@ -179,16 +179,13 @@
*
* Timeouts are implemented by means of timerfd timers, set based on flags:
*
- * - SYN_TIMEOUT_INIT: if no SYN,ACK is received from tap/guest during
- * handshake (flag ACK_FROM_TAP_DUE without ESTABLISHED event) within
- * this time, resend SYN. It's the starting timeout for the first SYN
- * retry. Retry for TCP_MAX_RETRIES or (syn_retries + syn_linear_timeouts)
- * times, reset the connection
- *
- * - ACK_TIMEOUT: if no ACK segment was received from tap/guest, after sending
- * data (flag ACK_FROM_TAP_DUE with ESTABLISHED event), re-send data from the
- * socket and reset sequence to what was acknowledged. If this persists for
- * more than TCP_MAX_RETRIES times in a row, reset the connection
+ * - RTO_INIT: if no ACK segment was received from tap/guest, either during
+ * handshake (flag ACK_FROM_TAP_DUE without ESTABLISHED event) or after
+ * sending data (flag ACK_FROM_TAP_DUE with ESTABLISHED event), re-send data
+ * from the socket and reset sequence to what was acknowledged. This is the
+ * timeout for the first retry, in seconds. Retry for TCP_MAX_RETRIES times
+ * for established connections, or (syn_retries + syn_linear_timeouts) times
+ * during the handshake, reset the connection
*
* - FIN_TIMEOUT: if a FIN segment was sent to tap/guest (flag ACK_FROM_TAP_DUE
* with TAP_FIN_SENT event), and no ACK is received within this time, reset
@@ -342,8 +339,7 @@ enum {
#define WINDOW_DEFAULT 14600 /* RFC 6928 */
#define ACK_INTERVAL 10 /* ms */
-#define SYN_TIMEOUT_INIT 1 /* s, RFC 6928 */
-#define ACK_TIMEOUT 2
+#define RTO_INIT 1 /* s, RFC 6298 */
#define FIN_TIMEOUT 60
#define ACT_TIMEOUT 7200
@@ -594,13 +590,10 @@ static void tcp_timer_ctl(const struct ctx *c, struct tcp_tap_conn *conn)
if (conn->flags & ACK_TO_TAP_DUE) {
it.it_value.tv_nsec = (long)ACK_INTERVAL * 1000 * 1000;
} else if (conn->flags & ACK_FROM_TAP_DUE) {
- if (!(conn->events & ESTABLISHED)) {
- int exp;
- exp = (int)conn->retries - c->tcp.syn_linear_timeouts;
- it.it_value.tv_sec = SYN_TIMEOUT_INIT << MAX(exp, 0);
- } else {
- it.it_value.tv_sec = ACK_TIMEOUT;
- }
+ int exp = conn->retries;
+ if (!(conn->events & ESTABLISHED))
+ exp -= c->tcp.syn_linear_timeouts;
+ it.it_value.tv_sec = RTO_INIT << MAX(exp, 0);
} else if (CONN_HAS(conn, SOCK_FIN_SENT | TAP_FIN_ACKED)) {
it.it_value.tv_sec = FIN_TIMEOUT;
} else {
--
2.51.1
next prev parent reply other threads:[~2025-11-25 7:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 7:26 [PATCH v9 0/5] Retry SYNs for inbound connections Yumei Huang
2025-11-25 7:26 ` [PATCH v9 1/5] tcp: Rename "retrans" to "retries" Yumei Huang
2025-11-25 7:26 ` [PATCH v9 2/5] util: Introduce read_file() and read_file_integer() function Yumei Huang
2025-11-26 4:07 ` David Gibson
2025-11-27 22:33 ` Stefano Brivio
2025-11-25 7:26 ` [PATCH v9 3/5] tcp: Resend SYN for inbound connections Yumei Huang
2025-11-26 4:12 ` David Gibson
2025-11-25 7:26 ` Yumei Huang [this message]
2025-11-27 22:33 ` [PATCH v9 4/5] tcp: Update data retransmission timeout Stefano Brivio
2025-11-25 7:26 ` [PATCH v9 5/5] tcp: Clamp the retry timeout Yumei Huang
2025-11-26 4:15 ` David Gibson
2025-11-27 22:33 ` Stefano Brivio
2025-12-01 4:09 ` Yumei Huang
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=20251125072638.88896-5-yuhuang@redhat.com \
--to=yuhuang@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).