Netdev List
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Emil Tsalapatis <emil@etsalapatis.com>,
	netdev@vger.kernel.org, edumazet@google.com
Cc: ncardwell@google.com, kuniyu@google.com, davem@davemloft.net,
	kuba@kernel.org
Subject: Re: [PATCH net-next] net/tcp: Prevent inlining tcp_syn_ack_timeout()
Date: Tue, 21 Jul 2026 15:24:52 +0200	[thread overview]
Message-ID: <6c01c713-14a8-43c2-aaaf-2fcf622f7e4f@redhat.com> (raw)
In-Reply-To: <20260708180837.9507-1-emil@etsalapatis.com>

On 7/8/26 8:08 PM, Emil Tsalapatis wrote:
> The tcp_syn_ack_timeout() function gets inlined by Clang,
> preventing tracing. Since the call is not in the fast
> path, prevent it from being inlined.
> 
> Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
> ---
>  net/ipv4/tcp_timer.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/net/ipv4/tcp_timer.c b/net/ipv4/tcp_timer.c
> index bf171b5e1eb3..f7215d53bbda 100644
> --- a/net/ipv4/tcp_timer.c
> +++ b/net/ipv4/tcp_timer.c
> @@ -748,7 +748,7 @@ static void tcp_write_timer(struct timer_list *t)
>  	sock_put(sk);
>  }
>  
> -void tcp_syn_ack_timeout(const struct request_sock *req)
> +noinline_for_tracing void tcp_syn_ack_timeout(const struct request_sock *req)
>  {
>  	struct net *net = read_pnet(&inet_rsk(req)->ireq_net);
>  

What's the point of tracing such function? It just increment a mib. If
you want to discriminate between TFO and non TFO syn ack timeout,
possibly adding another MIB counter and incrementing it in
tcp_fastopen_synack_timer() would be better???

/P


  reply	other threads:[~2026-07-21 13:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 18:08 [PATCH net-next] net/tcp: Prevent inlining tcp_syn_ack_timeout() Emil Tsalapatis
2026-07-21 13:24 ` Paolo Abeni [this message]
2026-07-21 14:18   ` Eric Dumazet
2026-07-21 15:12   ` Jakub Kicinski
2026-07-21 16:03     ` Paolo Abeni
2026-07-21 16:20 ` 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=6c01c713-14a8-43c2-aaaf-2fcf622f7e4f@redhat.com \
    --to=pabeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=emil@etsalapatis.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=ncardwell@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox