From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Cc: jhs@mojatatu.com, Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH net-next v5 0/5] net/sched: netem: enhancements
Date: Sat, 9 May 2026 10:03:21 -0700 [thread overview]
Message-ID: <20260509171123.307549-1-stephen@networkplumber.org> (raw)
This is a collection of improvements to netem found while
investigating the fixes now in net tree.
v5 - minor cleanups
- add allocation_errors counter
- align counters with where impairment occurs
Stephen Hemminger (5):
net/sched: netem: reorder struct netem_sched_data
net/sched: netem: remove useless VERSION
net/sched: netem: replace pr_info with netlink extack error messages
net/sched: netem: handle multi-segment skb in corruption
net/sched: netem: add per-impairment extended statistics
include/uapi/linux/pkt_sched.h | 10 ++
net/sched/sch_netem.c | 223 ++++++++++++++++++++-------------
2 files changed, 144 insertions(+), 89 deletions(-)
--
2.53.0
next reply other threads:[~2026-05-09 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 17:03 Stephen Hemminger [this message]
2026-05-09 17:03 ` [PATCH net-next v5 1/5] net/sched: netem: reorder struct netem_sched_data Stephen Hemminger
2026-05-09 17:03 ` [PATCH net-next v5 2/5] net/sched: netem: remove useless VERSION Stephen Hemminger
2026-05-09 17:03 ` [PATCH net-next v5 3/5] net/sched: netem: replace pr_info with netlink extack error messages Stephen Hemminger
2026-05-09 17:03 ` [PATCH net-next v5 4/5] net/sched: netem: handle multi-segment skb in corruption Stephen Hemminger
2026-05-09 17:03 ` [PATCH net-next v5 5/5] net/sched: netem: add per-impairment extended statistics Stephen Hemminger
2026-05-12 8:58 ` Stephen Hemminger
2026-05-14 10:00 ` [PATCH net-next v5 0/5] net/sched: netem: enhancements 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=20260509171123.307549-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=jhs@mojatatu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.