From: Paolo Abeni <pabeni@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] net/sched: netem: cleanups and improvements
Date: Mon, 30 Mar 2026 10:16:21 +0200 [thread overview]
Message-ID: <4400db54-aaf0-4cc4-98b5-bdee35e29cce@redhat.com> (raw)
In-Reply-To: <20260328182704.456993-1-stephen@networkplumber.org>
On 3/28/26 7:26 PM, Stephen Hemminger wrote:
> Cleanup and improvement patches for netem, done as follow-on
> to the bug fix series found during AI-assisted review.
>
> - replace pr_info() with netlink extack error reporting
> - validate slot min/max delay range on configuration
> - fix slot delay calculation overflow for large ranges
> - remove unused loss model struct fields
> - remove stale VERSION string
> - add per-impairment extended statistics (delayed, dropped,
> corrupted, duplicated, reordered, ecn_marked)
>
> The xstats patch requires a corresponding iproute2 change
> to display the new counters in tc -s qdisc show. This will go
> as separate patch after this.
>
> Stephen Hemminger (6):
> net/sched: netem: replace pr_info with netlink extack error messages
> net/sched: netem: check for invalid slot range
> net/sched: netem: fix slot delay calculation overflow
> net/sched: netem: remove unused loss model fields
> net/sched: netem: remove useless VERSION
> net/sched: netem: add per-impairment extended statistics
>
> include/uapi/linux/pkt_sched.h | 9 +++
> net/sched/sch_netem.c | 120 ++++++++++++++++++++++-----------
> 2 files changed, 89 insertions(+), 40 deletions(-)
I wild guess this is causing TDC failures:
# not ok 364 8c17 - Test netem's recursive duplicate
# Value doesn't match: bytes: 294 != 196
# Matching against output: {'kind': 'netem', 'handle': '1:', 'root':
True, 'refcnt': 2, 'options': {'limit': 1, 'duplicate': {'duplicate': 1,
'correlation': 0}, 'seed': 6495514880116664183, 'ecn': False, 'gap': 0},
'bytes': 196, 'packets': 2, 'drops': 1, 'overlimits': 0, 'requeues': 0,
'backlog': 0, 'qlen': 0}
Possibly patch 6/6 needs to update the expected netem output accordingly?!?
Also there are a is a checkpatch issue on patch 2/6 (empty line between
fixes tag and SoB). Tentatively set this revision to 'changes requested'.
/P
next prev parent reply other threads:[~2026-03-30 8:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 18:26 [PATCH net-next 0/6] net/sched: netem: cleanups and improvements Stephen Hemminger
2026-03-28 18:26 ` [PATCH net-next 1/6] net/sched: netem: replace pr_info with netlink extack error messages Stephen Hemminger
2026-03-28 18:26 ` [PATCH net-next 2/6] net/sched: netem: check for invalid slot range Stephen Hemminger
2026-03-31 0:32 ` Jakub Kicinski
2026-03-28 18:26 ` [PATCH net-next 3/6] net/sched: netem: fix slot delay calculation overflow Stephen Hemminger
2026-03-28 18:26 ` [PATCH net-next 4/6] net/sched: netem: remove unused loss model fields Stephen Hemminger
2026-03-28 18:26 ` [PATCH net-next 5/6] net/sched: netem: remove useless VERSION Stephen Hemminger
2026-03-28 18:26 ` [PATCH net-next 6/6] net/sched: netem: add per-impairment extended statistics Stephen Hemminger
2026-03-30 8:16 ` Paolo Abeni [this message]
2026-03-30 14:49 ` [PATCH net-next 0/6] net/sched: netem: cleanups and improvements Stephen Hemminger
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=4400db54-aaf0-4cc4-98b5-bdee35e29cce@redhat.com \
--to=pabeni@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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