[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250210004346.50931-1-kuniyu@amazon.com>
Date: Mon, 10 Feb 2025 09:43:46 +0900
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <edumazet@...gle.com>
CC: <davem@...emloft.net>, <eric.dumazet@...il.com>, <horms@...nel.org>,
<kernelxing@...cent.com>, <kuba@...nel.org>, <kuniyu@...zon.com>,
<ncardwell@...gle.com>, <netdev@...r.kernel.org>, <pabeni@...hat.com>
Subject: Re: [PATCH net-next 4/5] tcp: add the ability to control max RTO
From: Eric Dumazet <edumazet@...gle.com>
Date: Fri, 7 Feb 2025 15:28:29 +0000
> Currently, TCP stack uses a constant (120 seconds)
> to limit the RTO value exponential growth.
>
> Some applications want to set a lower value.
>
> Add TCP_RTO_MAX_MS socket option to set a value (in ms)
> between 1 and 120 seconds.
>
> It is discouraged to change the socket rto max on a live
> socket, as it might lead to unexpected disconnects.
>
> Following patch is adding a netns sysctl to control the
> default value at socket creation time.
>
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
Reviewed-by: Kuniyuki Iwashima <kuniyu@...zon.com>
Powered by blists - more mailing lists