From: David Gibson <david@gibson.dropbear.id.au>
To: Yumei Huang <yuhuang@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Subject: Re: [PATCH v7 5/5] tcp: Clamp the retry timeout
Date: Mon, 3 Nov 2025 20:37:57 +1100 [thread overview]
Message-ID: <aQh39fnFiHy2MbGK@zatzit> (raw)
In-Reply-To: <CANsz47njsChM5S5vWn5qM-zC2eADUujCDvyuF9VLGK41Gndmfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]
On Mon, Nov 03, 2025 at 11:11:10AM +0800, Yumei Huang wrote:
> On Fri, Oct 31, 2025 at 4:38 PM Stefano Brivio <sbrivio@redhat.com> wrote:
> >
> > On Fri, 31 Oct 2025 13:42:42 +0800
> > Yumei Huang <yuhuang@redhat.com> wrote:
[snip]
> > > diff --git a/tcp.h b/tcp.h
> > > index befedde..a238bb7 100644
> > > --- a/tcp.h
> > > +++ b/tcp.h
> > > @@ -59,6 +59,7 @@ 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_rto_max: Maximal retry timeout (in s)
> >
> > Nit: "maximal" has a slightly different meaning compared to "maximum".
> >
> > The highest value allowed for a field would typically be called
> > "maximum", while "maximal" is more commonly used to indicate a value /
> > element that's the biggest of all values. Yes, I know, it's complicated.
>
> Yeah, it's complicated. Actually I get the word from networking/ip-sysctl.rst.
>
> tcp_rto_max_ms - INTEGER
> Maximal TCP retransmission timeout (in ms).
>
> "maximum" might be more appropriate as you explained.
In mathematics, the difference is well defined. "maximal" means
nothing else is bigger than it, "maximum" means everything else is
smaller than it. Those are the same thing for a total order, but not
for a partial order.
Since integers have a total order, either would be correct here,
according to mathematician's English.
Of course, that only partly overlaps with everyday English usage. I
think either would be fine, but "maximum" is probably slightly better.
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-11-03 10:51 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 for inbound connections 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
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 [this message]
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=aQh39fnFiHy2MbGK@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
--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).