mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: netdev-bot+sashiko@kernel.org
To: hemendranaik@gmail.com
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	jiri@resnulli.us, jhs@mojatatu.com, shuah@kernel.org,
	donald.hunter@gmail.com, ast@fiberby.net, toke@redhat.com,
	liuhangbin@kylinos.cn, j.koeppeler@tu-berlin.de,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	vishy0777@gmail.com, tahiliani@nitk.edu.in
Subject: Re: [PATCH net-next v10 3/4] net/sched: pie: correct tc_pie_xstats field documentation
Date: Wed, 11 Nov 2026 19:11:53 +0000	[thread overview]
Message-ID: <179442431354.2199510.17171987421866459673@kernel.org> (raw)
In-Reply-To: <20261109071017.438478-4-hemendranaik@gmail.com>

Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.

Low priority / nit picks for your consideration:

- [Low] The patch fixes the unit comments for struct tc_pie_xstats in
  include/uapi/linux/pkt_sched.h: delay is now 'microseconds' and…

--

net/sched: pie: correct tc_pie_xstats field documentation

This patch updates the comments on struct tc_pie_xstats in the uapi header.
The delay field is now documented as microseconds and avg_dq_rate as
bytes/second, which matches what pie_dump_stats() exports. There is no
change to the UAPI layout or to runtime behaviour.

> diff --git a/include/uapi/linux/pkt_sched.h b/include/uapi/linux/pkt_sched.h
> index fef848eaaab23..445a041cd103f 100644
> --- a/include/uapi/linux/pkt_sched.h
> +++ b/include/uapi/linux/pkt_sched.h
> @@ -920,9 +920,9 @@ enum {
>  
>  struct tc_pie_xstats {
>  	__u64 prob;			/* current probability */
> -	__u32 delay;			/* current delay in ms */
> +	__u32 delay;			/* current delay in microseconds */
>  	__u32 avg_dq_rate;		/* current average dq_rate in
> -					 * bits/pie_time
> +					 * bytes/second
>  					 */

[Severity: Low]
Should the netlink YAML spec for this struct get the same correction?

The tc-pie-xstats definition in Documentation/netlink/specs/tc.yaml still
uses the old units:

        name: delay
        type: u32
        doc: Current delay in ms
      -
        name: avg-dq-rate
        type: u32
        doc: Current average dq rate in bits/pie-time

pie_dump_stats() in net/sched/sch_pie.c exports microseconds and
bytes/second:

	.delay = ((u32)PSCHED_TICKS2NS(READ_ONCE(q->vars.qdelay))) / NSEC_PER_USEC,
	...
	st.avg_dq_rate = READ_ONCE(q->vars.avg_dq_rate) *
			 (PSCHED_TICKS_PER_SEC) >> PIE_SCALE;

With this patch applied, the header and the YAML spec give different units
for the same uAPI struct.

The later commit "Documentation/netlink/specs: tc: describe fq_pie per-flow
class stats" edits tc.yaml. It documents the matching fq_pie fields as
microseconds and bytes/second, but leaves tc-pie-xstats as it is, so tc.yaml
contradicts itself at the end of the series.

The commit message says:

    Touch include/uapi/linux/pkt_sched.h only

Could tc.yaml be updated here as well, or in a follow-up patch?

>  	__u32 dq_rate_estimating;	/* is avg_dq_rate being calculated? */
>  	__u32 packets_in;		/* total number of packets enqueued */

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261109071017.438478-1-hemendranaik%40gmail.com

  reply	other threads:[~2026-11-11 19:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  7:10 [PATCH net-next v10 0/4] net/sched: sch_fq_pie: add per-flow class statistics Hemendra M. Naik
2026-11-09  7:10 ` [PATCH net-next v10 1/4] net/sched: sch_fq_pie: add per-flow statistics via class ops Hemendra M. Naik
2026-11-11 19:11   ` netdev-bot+sashiko
2026-11-09  7:10 ` [PATCH net-next v10 2/4] selftests: tc-testing: add fq_pie per-flow class stats test Hemendra M. Naik
2026-11-11 19:11   ` netdev-bot+sashiko
2026-11-09  7:10 ` [PATCH net-next v10 3/4] net/sched: pie: correct tc_pie_xstats field documentation Hemendra M. Naik
2026-11-11 19:11   ` netdev-bot+sashiko [this message]
2026-11-09  7:10 ` [PATCH net-next v10 4/4] Documentation/netlink/specs: tc: describe fq_pie per-flow class stats Hemendra M. Naik
2026-11-11 19:11   ` netdev-bot+sashiko

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=179442431354.2199510.17171987421866459673@kernel.org \
    --to=netdev-bot+sashiko@kernel.org \
    --cc=ast@fiberby.net \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@kernel.org \
    --cc=hemendranaik@gmail.com \
    --cc=horms@kernel.org \
    --cc=j.koeppeler@tu-berlin.de \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@kylinos.cn \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=tahiliani@nitk.edu.in \
    --cc=toke@redhat.com \
    --cc=vishy0777@gmail.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

all inboxes | Powered by JetHome®