From: David Ahern <dsahern@kernel.org>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] inet_diag: report delayed ack timer information
Date: Wed, 4 Mar 2026 08:48:53 -0700 [thread overview]
Message-ID: <93b5fb6d-7aa0-481f-823f-995ed8ab0e52@kernel.org> (raw)
In-Reply-To: <20260304094318.1769536-1-edumazet@google.com>
On 3/4/26 2:43 AM, Eric Dumazet wrote:
> inet_sk_diag_fill() populates r->idiag_timer with the following
> precedence order:
>
> 1 - Retransmit timer.
> 4 - Probe0 timer.
> 2 - Keepalive timer.
>
> This patch adds a new value, last in the list, if other timers
> are not active.
>
> 5 - Delayed ACK timer.
>
> A corresponding iproute2 patch is needed to replace "unknown"
> with "delack":
...
> diff --git a/net/ipv4/inet_diag.c b/net/ipv4/inet_diag.c
> index 9d215485b5c7e7ba29dd53c924f0245439d74af5..e4cb18061aefcc22df04644c00bf5c7db4e150d2 100644
> --- a/net/ipv4/inet_diag.c
> +++ b/net/ipv4/inet_diag.c
> @@ -298,6 +298,10 @@ int inet_sk_diag_fill(struct sock *sk, struct inet_connection_sock *icsk,
> r->idiag_retrans = READ_ONCE(icsk->icsk_probes_out);
> r->idiag_expires =
> jiffies_delta_to_msecs(icsk->icsk_keepalive_timer.expires - jiffies);
> + } else if (timer_pending(&icsk->icsk_delack_timer)) {
> + r->idiag_timer = 5;
How come the idiag_timer values an enum in
include/uapi/linux/inet_diag.h since this is a uapi?
> + r->idiag_expires =
> + jiffies_delta_to_msecs(icsk_delack_timeout(icsk) - jiffies);
> }
>
> if ((ext & (1 << (INET_DIAG_INFO - 1))) && handler->idiag_info_size) {
next prev parent reply other threads:[~2026-03-04 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 9:43 [PATCH net-next] inet_diag: report delayed ack timer information Eric Dumazet
2026-03-04 15:48 ` David Ahern [this message]
2026-03-04 16:00 ` Eric Dumazet
2026-03-04 16:55 ` Eric Dumazet
2026-03-04 17:01 ` Neal Cardwell
2026-03-04 17:02 ` David Ahern
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=93b5fb6d-7aa0-481f-823f-995ed8ab0e52@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox