From: Stefano Brivio <sbrivio@redhat.com>
To: Yumei Huang <yuhuang@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>, passt-dev@passt.top
Subject: Re: [PATCH v2 2/3] tcp: Resend SYN for inbound connections
Date: Mon, 13 Oct 2025 12:31:25 +0200 [thread overview]
Message-ID: <20251013123125.6bcc8b9d@elisabeth> (raw)
In-Reply-To: <CANsz47m-+f7J44NfgUAyUczDbJ7z4zura3oUyd+G=yDnau=0EQ@mail.gmail.com>
On Mon, 13 Oct 2025 18:22:00 +0800
Yumei Huang <yuhuang@redhat.com> wrote:
> On Mon, Oct 13, 2025 at 8:21 AM David Gibson
> <david@gibson.dropbear.id.au> wrote:
> >
> > On Fri, Oct 10, 2025 at 03:46:59PM +0800, Yumei Huang wrote:
> > >
> > > +/**
> > > + * get_tcp_syn_param() - Read SYN parameters from /proc/sys
> > > + * @path: Path to the sysctl file
> > > + * @fallback: Default value if file can't be read
> > > + *
> > > + * Return: Parameter value, fallback on failure
> > > +*/
> > > +int get_tcp_syn_param(const char *path, int fallback)
> >
> > I wonder if it might be worth making a new function in util.c to read
> > a file containing a single number.
>
> I can do that. So it could be reused in the future.
If it helps: we already have write_file(), so it might be worth adding
a read_file() symmetric to it. Maybe it's overkill though.
--
Stefano
next prev parent reply other threads:[~2025-10-13 10:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 7:46 [PATCH v2 0/3] Retry SYNs " Yumei Huang
2025-10-10 7:46 ` [PATCH v2 1/3] tcp: Rename "retrans" to "retries" Yumei Huang
2025-10-12 23:52 ` David Gibson
2025-10-10 7:46 ` [PATCH v2 2/3] tcp: Resend SYN for inbound connections Yumei Huang
2025-10-13 0:18 ` David Gibson
2025-10-13 10:22 ` Yumei Huang
2025-10-13 10:31 ` Stefano Brivio [this message]
2025-10-14 0:44 ` David Gibson
2025-10-14 0:42 ` David Gibson
2025-10-10 7:47 ` [PATCH v2 3/3] tcp: Update data retransmission timeout Yumei Huang
2025-10-13 0:29 ` David Gibson
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=20251013123125.6bcc8b9d@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).