netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: edumazet@google.com, davem@davemloft.net, dsahern@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, apetlund@simula.no,
	netdev@vger.kernel.org, Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net] net: fix the RTO timer retransmitting skb every 1ms if linear option is enabled
Date: Thu, 10 Aug 2023 22:32:36 +0200	[thread overview]
Message-ID: <ZNVJZKBA698aRXmR@vergenet.net> (raw)
In-Reply-To: <20230810112148.2032-1-kerneljasonxing@gmail.com>

On Thu, Aug 10, 2023 at 07:21:48PM +0800, Jason Xing wrote:
> From: Jason Xing <kernelxing@tencent.com>
> 
> In the real workload, I encountered an issue which could cause the RTO
> timer to retransmit the skb per 1ms with linear option enabled. The amount
> of lost-retransmitted skbs can go up to 1000+ instantly.
> 
> The root cause is that if the icsk_rto happens to be zero in the 6th round
> (which is the TCP_THIN_LINEAR_RETRIES value), then it will alway be zero

nit: alway -> always

     checkpatch.pl --codespell is your friend

> due to the changed calculation method in tcp_retransmit_timer() as follows:
> 
> icsk->icsk_rto = min(icsk->icsk_rto << 1, TCP_RTO_MAX);
> 
> Above line could be converted to
> icsk->icsk_rto = min(0 << 1, TCP_RTO_MAX) = 0
> 
> Therefore, the timer expires so quickly without any doubt.
> 
> I read through the RFC 6298 and found that the RTO value can be rounded
> up to a certain value, in Linux, say TCP_RTO_MIN as default, which is
> regarded as the lower bound in this patch as suggested by Eric.
> 
> Fixes: 36e31b0af587 ("net: TCP thin linear timeouts")
> Suggested-by: Eric Dumazet <edumazet@google.com>
> Signed-off-by: Jason Xing <kernelxing@tencent.com>
> ---
>  net/ipv4/tcp_timer.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/net/ipv4/tcp_timer.c b/net/ipv4/tcp_timer.c
> index d45c96c7f5a4..b2b25861355c 100644
> --- a/net/ipv4/tcp_timer.c
> +++ b/net/ipv4/tcp_timer.c
> @@ -599,7 +599,9 @@ void tcp_retransmit_timer(struct sock *sk)
>  	    tcp_stream_is_thin(tp) &&
>  	    icsk->icsk_retransmits <= TCP_THIN_LINEAR_RETRIES) {
>  		icsk->icsk_backoff = 0;
> -		icsk->icsk_rto = min(__tcp_set_rto(tp), TCP_RTO_MAX);
> +		icsk->icsk_rto = clamp(__tcp_set_rto(tp),
> +					    tcp_rto_min(sk),
> +					    TCP_RTO_MAX);

nit: this indentation looks a bit odd.

		icsk->icsk_rto = clamp(__tcp_set_rto(tp),
				       tcp_rto_min(sk),
				       TCP_RTO_MAX);

>  	} else if (sk->sk_state != TCP_SYN_SENT ||
>  		   icsk->icsk_backoff >
>  		   READ_ONCE(net->ipv4.sysctl_tcp_syn_linear_timeouts)) {
> -- 
> 2.37.3
> 
> 

  reply	other threads:[~2023-08-10 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 11:21 [PATCH net] net: fix the RTO timer retransmitting skb every 1ms if linear option is enabled Jason Xing
2023-08-10 20:32 ` Simon Horman [this message]
2023-08-11  2:35   ` Jason Xing

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=ZNVJZKBA698aRXmR@vergenet.net \
    --to=horms@kernel.org \
    --cc=apetlund@simula.no \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kerneljasonxing@gmail.com \
    --cc=kernelxing@tencent.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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.
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).