From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Yumei Huang <yuhuang@redhat.com>, passt-dev@passt.top
Subject: Re: [PATCH v7 3/5] tcp: Resend SYN for inbound connections
Date: Wed, 5 Nov 2025 08:00:57 +0100 [thread overview]
Message-ID: <20251105080057.3c4a61b9@elisabeth> (raw)
In-Reply-To: <aQrRjFegJXDEjwf3@zatzit>
On Wed, 5 Nov 2025 15:24:44 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Tue, Nov 04, 2025 at 05:42:33AM +0100, Stefano Brivio wrote:
> > On Fri, 31 Oct 2025 13:42:40 +0800
> > Yumei Huang <yuhuang@redhat.com> wrote:
> [snip]
> > > +/**
> > > + * tcp_get_rto_params() - Get host kernel RTO parameters
> > > + * @c: Execution context
> > > +*/
> > > +void tcp_get_rto_params(struct ctx *c)
> > > +{
> > > + intmax_t tcp_syn_retries, syn_linear_timeouts;
> > > +
> > > + tcp_syn_retries = read_file_integer(
> > > + TCP_SYN_RETRIES, TCP_SYN_RETRIES_DEFAULT);
> > > + syn_linear_timeouts = read_file_integer(
> > > + TCP_SYN_LINEAR_TIMEOUTS, TCP_SYN_LINEAR_TIMEOUTS_DEFAULT);
> >
> > I think this is a bit hard to read. Now:
> >
> > tcp_syn_retries = read_file_integer(TCP_SYN_RETRIES,
> > TCP_SYN_RETRIES_DEFAULT);
> > syn_linear_timeouts = read_file_integer(TCP_SYN_LINEAR_TIMEOUTS,
> > TCP_SYN_LINEAR_TIMEOUTS_DEFAULT);
> >
> > would be a bit closer to the coding style we're adopting, but I wonder:
> >
> > - does read_file_integer() really need to have "integer" in the name?
>
> > In a language where integers are called 'int', perhaps
> > read_file_int() is clear enough?
>
> I think the idea is that read_file_integer() can be used for any
> (signed) integer type (with range checking performed after the call).
> read_file_int() might suggest it reads exactly an 'int', not anything
> bigger or smaller.
Oh, I see. It could be read_file_num() then, even if it's slightly less
accurate, or it can even remain read_file_integer(). If something like
this:
v = read_file_integer(SYN_RETRIES, SYN_RETRIES_DEFAULT);
c->tcp.tcp_syn_retries = MIN(v, UINT8_MAX);
v = read_file_integer(SYN_LINEAR_TIMEOUTS, SYN_LINEAR_TIMEOUTS_DEFAULT);
c->tcp.syn_linear_timeouts = MIN(v, UINT8_MAX);
fits 80 columns, I'm taking it as a sign that the function name isn't
exceedingly long. No particular preference from me.
> > - the constants are defined here, in tcp.c, so they obviously refer to
> > TCP, so maybe SYN_LINEAR_TIMEOUTS is clear enough
> >
> > - you don't really need to store both values in two different
> > variables, one is enough as you're assigning them right away. And:
> >
> > v = read_file_int(SYN_RETRIES, SYN_RETRIES_DEFAULT);
> > c->tcp.tcp_syn_retries = MIN(v, UINT8_MAX);
> >
> > v = read_file_int(SYN_LINEAR_TIMEOUTS, SYN_LINEAR_TIMEOUTS_DEFAULT);
> > c->tcp.syn_linear_timeouts = MIN(v, UINT8_MAX);
> >
> > is four lines instead of six, and more readable if you ask me.
> >
> > > +
> > > + c->tcp.tcp_syn_retries = MIN(tcp_syn_retries, UINT8_MAX);
> > > + c->tcp.syn_linear_timeouts = MIN(syn_linear_timeouts, UINT8_MAX);
> > > +
> > > + debug("Read sysctl values tcp_syn_retries: %"PRIu8", linear_timeouts: %"PRIu8,
> > > + c->tcp.tcp_syn_retries, c->tcp.syn_linear_timeouts);
> > > +}
> > > +
> > > /**
> > > * tcp_init() - Get initial sequence, hash secret, initialise per-socket data
> > > * @c: Execution context
> > > @@ -2776,6 +2815,8 @@ int tcp_init(struct ctx *c)
> > > {
> > > ASSERT(!c->no_tcp);
> > >
> > > + tcp_get_rto_params(c);
> > > +
> > > tcp_sock_iov_init(c);
> > >
> > > memset(init_sock_pool4, 0xff, sizeof(init_sock_pool4));
> > > diff --git a/tcp.h b/tcp.h
> > > index 234a803..befedde 100644
> > > --- a/tcp.h
> > > +++ b/tcp.h
> > > @@ -59,12 +59,16 @@ union tcp_listen_epoll_ref {
> > > * @fwd_out: Port forwarding configuration for outbound packets
> > > * @timer_run: Timestamp of most recent timer run
> > > * @pipe_size: Size of pipes for spliced connections
> > > + * @tcp_syn_retries: SYN retries using exponential backoff timeout
> > > + * @syn_linear_timeouts: SYN retries before using exponential backoff timeout
> > > */
> > > struct tcp_ctx {
> > > struct fwd_ports fwd_in;
> > > struct fwd_ports fwd_out;
> > > struct timespec timer_run;
> > > size_t pipe_size;
> > > + uint8_t tcp_syn_retries;
> >
> > Why 'tcp' again?
> >
> > > + uint8_t syn_linear_timeouts;
> > > };
> > >
> > > #endif /* TCP_H */
--
Stefano
next prev parent reply other threads:[~2025-11-05 7:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 5:42 [PATCH v7 0/5] Retry SYNs " Yumei Huang
2025-10-31 5:42 ` [PATCH v7 1/5] tcp: Rename "retrans" to "retries" Yumei Huang
2025-10-31 5:42 ` [PATCH v7 2/5] util: Introduce read_file() and read_file_integer() function Yumei Huang
2025-11-03 0:53 ` David Gibson
2025-10-31 5:42 ` [PATCH v7 3/5] tcp: Resend SYN for inbound connections Yumei Huang
2025-11-03 1:09 ` David Gibson
2025-11-03 2:31 ` Yumei Huang
2025-11-03 9:01 ` David Gibson
2025-11-04 4:42 ` Stefano Brivio
2025-11-04 4:42 ` Stefano Brivio
2025-11-05 4:24 ` David Gibson
2025-11-05 7:00 ` Stefano Brivio [this message]
2025-11-07 9:56 ` Yumei Huang
2025-11-07 10:05 ` Stefano Brivio
2025-11-10 2:52 ` Yumei Huang
2025-11-10 4:25 ` David Gibson
2025-10-31 5:42 ` [PATCH v7 4/5] tcp: Update data retransmission timeout Yumei Huang
2025-10-31 5:56 ` Yumei Huang
2025-10-31 8:04 ` Stefano Brivio
2025-11-03 1:18 ` David Gibson
2025-11-03 2:57 ` Yumei Huang
2025-11-03 9:32 ` David Gibson
2025-11-04 4:42 ` Stefano Brivio
2025-11-05 4:19 ` David Gibson
2025-10-31 5:42 ` [PATCH v7 5/5] tcp: Clamp the retry timeout Yumei Huang
2025-10-31 8:38 ` Stefano Brivio
2025-11-03 3:11 ` Yumei Huang
2025-11-03 9:37 ` David Gibson
2025-11-03 10:55 ` Stefano Brivio
2025-11-03 1:37 ` David Gibson
2025-11-03 4:06 ` Yumei Huang
2025-11-03 10:38 ` Stefano Brivio
2025-11-05 4:22 ` David Gibson
2025-11-04 4:42 ` Stefano Brivio
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=20251105080057.3c4a61b9@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=yuhuang@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).