From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 0/3] tcp: Runtime checks for availability of TCP_INFO fields
Date: Fri, 25 Oct 2024 15:38:41 +0200 [thread overview]
Message-ID: <20241025153841.40e61a16@elisabeth> (raw)
In-Reply-To: <20241024045922.3900584-1-david@gibson.dropbear.id.au>
On Thu, 24 Oct 2024 15:59:19 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> We have a number of Makefile tests for the presence of various fields
> in tcp_info. However that only tells us if they're present in the
> kernel headers against which we're compiling, not whether they're
> available in the kernel we're running on. For anything outside the
> earliest forms of TCP_INFO (as described in netinet/tcp.h and shared
> with BSD), we should verify at runtime if the kernel is returning that
> information.
>
> This was supposed to be leading into improved handling of lazily
> calling TCP_INFO, but I hit additional complications there, so I've
> postponed it. Might as well get these bits merged, though.
>
> v2:
> * Previous version removed some #ifdefs that were still needed.
> Simply putting them back leads to awkward duplication between the
> "compile time missing" and "run time missing" cases, so take a
> different approach which allows us to remove all of them.
> * Some wording changes
Applied with a trivial s/we here define/we define here/ and
s/This taken/This is taken/ in 1/3.
--
Stefano
prev parent reply other threads:[~2024-10-25 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 4:59 [PATCH v2 0/3] tcp: Runtime checks for availability of TCP_INFO fields David Gibson
2024-10-24 4:59 ` [PATCH v2 1/3] tcp: Remove compile-time dependency on struct tcp_info version David Gibson
2024-10-24 4:59 ` [PATCH v2 2/3] tcp: Generalise probing for tcpi_snd_wnd field David Gibson
2024-10-24 4:59 ` [PATCH v2 3/3] tcp: Use runtime tests for TCP_INFO fields David Gibson
2024-10-25 13:38 ` Stefano Brivio [this message]
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=20241025153841.40e61a16@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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).