From: Jakub Kicinski <kuba@kernel.org>
To: "Hemendra M. Naik" <hemendranaik@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@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 0/4] net/sched: sch_fq_pie: add per-flow class statistics
Date: Mon, 16 Nov 2026 15:10:30 -0800 [thread overview]
Message-ID: <20261116151030.69ec14ae@kernel.org> (raw)
In-Reply-To: <20261109071017.438478-1-hemendranaik@gmail.com>
On Mon, 9 Nov 2026 12:40:13 +0530 Hemendra M. Naik wrote:
> FQ-PIE runs an independent PIE controller per flow but exposes no
> per-flow statistics. This series wires up fq_pie_class_ops to expose
> per-flow AQM state (prob, delay, deficit, avg_dq_rate) via
> 'tc -s class show', following a similar pattern as FQ-CoDel.
AI feedback looks at least 50% legit.
prev parent reply other threads:[~2026-11-16 23:10 UTC|newest]
Thread overview: 10+ 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
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
2026-11-16 23:10 ` Jakub Kicinski [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=20261116151030.69ec14ae@kernel.org \
--to=kuba@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=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