From: Jakub Kicinski <kuba@kernel.org>
To: Jie Meng <jmeng@fb.com>
Cc: <netdev@vger.kernel.org>, <kafai@fb.com>
Subject: Re: [PATCH net-next] tcp: Make SYN ACK RTO tunable by BPF programs with TFO
Date: Tue, 9 Aug 2022 22:11:01 -0700 [thread overview]
Message-ID: <20220809221101.30d59085@kernel.org> (raw)
In-Reply-To: <20220806000635.472853-1-jmeng@fb.com>
On Fri, 5 Aug 2022 17:06:35 -0700 Jie Meng 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.
Please make sure to CC the relevant maintainers
(./scripts/get_maintainer.pl). Apart from that:
# Form letter - net-next is closed
We have already sent the networking pull request for 6.0
and therefore net-next is closed for new drivers, features,
code refactoring and optimizations. We are currently accepting
bug fixes only.
Please repost when net-next reopens after 6.0-rc1 is cut.
RFC patches sent for review only are obviously welcome at any time.
next prev parent reply other threads:[~2022-08-10 5:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 0:06 [PATCH net-next] tcp: Make SYN ACK RTO tunable by BPF programs with TFO Jie Meng
2022-08-10 5:11 ` Jakub Kicinski [this message]
2022-08-10 22:30 ` Martin KaFai Lau
-- strict thread matches above, loose matches on Subject: below --
2022-08-15 20:29 Jie Meng
2022-08-16 13:36 ` Neal Cardwell
2022-08-16 16:11 ` Yuchung Cheng
2022-08-16 16:59 ` Martin KaFai Lau
2022-08-17 9:30 ` patchwork-bot+netdevbpf
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=20220809221101.30d59085@kernel.org \
--to=kuba@kernel.org \
--cc=jmeng@fb.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.