From: Neal Cardwell <ncardwell@google.com>
To: Jie Meng <jmeng@fb.com>
Cc: netdev@vger.kernel.org, kafai@fb.com, kuba@kernel.org,
edumazet@google.com, bpf@vger.kernel.org,
Yuchung Cheng <ycheng@google.com>, Wei Wang <weiwan@google.com>
Subject: Re: [PATCH net-next] tcp: Make SYN ACK RTO tunable by BPF programs with TFO
Date: Tue, 16 Aug 2022 09:36:44 -0400 [thread overview]
Message-ID: <CADVnQy=hav-cLt5Dy0DBPiDCxgkpRCEktEoMNjq_uKG8hynLPg@mail.gmail.com> (raw)
In-Reply-To: <20220815202900.3961097-1-jmeng@fb.com>
On Mon, Aug 15, 2022 at 8:30 PM Jie Meng <jmeng@fb.com> wrote:
>
> Instead of the hardcoded TCP_TIMEOUT_INIT, this diff calls tcp_timeout_init
> to initiate req->timeout like the non TFO SYN ACK case.
>
> Tested using the following packetdrill script, on a host with a BPF
> program that sets the initial connect timeout to 10ms.
>
> `../../common/defaults.sh`
>
> // Initialize connection
> 0 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3
> +0 setsockopt(3, SOL_TCP, TCP_FASTOPEN, [1], 4) = 0
> +0 bind(3, ..., ...) = 0
> +0 listen(3, 1) = 0
>
> +0 < S 0:0(0) win 32792 <mss 1000,sackOK,FO TFO_COOKIE>
> +0 > S. 0:0(0) ack 1 <mss 1460,nop,nop,sackOK>
> +.01 > S. 0:0(0) ack 1 <mss 1460,nop,nop,sackOK>
> +.02 > S. 0:0(0) ack 1 <mss 1460,nop,nop,sackOK>
> +.04 > S. 0:0(0) ack 1 <mss 1460,nop,nop,sackOK>
> +.01 < . 1:1(0) ack 1 win 32792
>
> +0 accept(3, ..., ...) = 4
>
> Signed-off-by: Jie Meng <jmeng@fb.com>
> ---
> net/ipv4/tcp_fastopen.c | 3 ++-
> net/ipv4/tcp_timer.c | 2 +-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv4/tcp_fastopen.c b/net/ipv4/tcp_fastopen.c
> index 825b216d11f5..45cc7f1ca296 100644
> --- a/net/ipv4/tcp_fastopen.c
> +++ b/net/ipv4/tcp_fastopen.c
> @@ -272,8 +272,9 @@ static struct sock *tcp_fastopen_create_child(struct sock *sk,
> * The request socket is not added to the ehash
> * because it's been added to the accept queue directly.
> */
> + req->timeout = tcp_timeout_init(child);
> inet_csk_reset_xmit_timer(child, ICSK_TIME_RETRANS,
> - TCP_TIMEOUT_INIT, TCP_RTO_MAX);
> + req->timeout, TCP_RTO_MAX);
>
> refcount_set(&req->rsk_refcnt, 2);
>
> diff --git a/net/ipv4/tcp_timer.c b/net/ipv4/tcp_timer.c
> index b4dfb82d6ecb..cb79127f45c3 100644
> --- a/net/ipv4/tcp_timer.c
> +++ b/net/ipv4/tcp_timer.c
> @@ -428,7 +428,7 @@ static void tcp_fastopen_synack_timer(struct sock *sk, struct request_sock *req)
> if (!tp->retrans_stamp)
> tp->retrans_stamp = tcp_time_stamp(tp);
> inet_csk_reset_xmit_timer(sk, ICSK_TIME_RETRANS,
> - TCP_TIMEOUT_INIT << req->num_timeout, TCP_RTO_MAX);
> + req->timeout << req->num_timeout, TCP_RTO_MAX);
> }
>
>
> --
Looks good to me. Thanks for the feature!
Acked-by: Neal Cardwell <ncardwell@google.com>
neal
next prev parent reply other threads:[~2022-08-16 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 20:29 [PATCH net-next] tcp: Make SYN ACK RTO tunable by BPF programs with TFO Jie Meng
2022-08-16 13:36 ` Neal Cardwell [this message]
2022-08-16 16:11 ` Yuchung Cheng
2022-08-16 16:59 ` Martin KaFai Lau
2022-08-17 9:30 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2022-08-06 0:06 Jie Meng
2022-08-10 5:11 ` Jakub Kicinski
2022-08-10 22:30 ` Martin KaFai Lau
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='CADVnQy=hav-cLt5Dy0DBPiDCxgkpRCEktEoMNjq_uKG8hynLPg@mail.gmail.com' \
--to=ncardwell@google.com \
--cc=bpf@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jmeng@fb.com \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=weiwan@google.com \
--cc=ycheng@google.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).