From: Jakub Kicinski <kuba@kernel.org>
To: Jesper Dangaard Brouer <hawk@kernel.org>
Cc: netdev@vger.kernel.org, "Eric Dumazet" <eric.dumazet@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Paolo Abeni" <pabeni@redhat.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
bpf@vger.kernel.org, horms@kernel.org, jiri@resnulli.us,
edumazet@google.com, xiyou.wangcong@gmail.com, jhs@mojatatu.com,
carges@cloudflare.com, kernel-team@cloudflare.com
Subject: Re: [PATCH net-next RFC v1 0/3] net: sched: refactor qdisc drop reasons into dedicated tracepoint
Date: Wed, 4 Feb 2026 19:04:17 -0800 [thread overview]
Message-ID: <20260204190417.110f5498@kernel.org> (raw)
In-Reply-To: <177022452988.1827734.5121740962985640333.stgit@firesoul>
On Wed, 04 Feb 2026 18:02:49 +0100 Jesper Dangaard Brouer wrote:
> RFC: Seeking feedback on this refactoring approach.
>
> This series refactors qdisc drop reason handling by introducing a dedicated
> enum qdisc_drop_reason and trace_qdisc_drop tracepoint, providing qdisc
> layer drop diagnostics with direct qdisc context visibility.
I like this!
It will presumably require existing users to migrate over
but sooner we do it the fewer users that have to move?
next prev parent reply other threads:[~2026-02-05 3:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 17:02 [PATCH net-next RFC v1 0/3] net: sched: refactor qdisc drop reasons into dedicated tracepoint Jesper Dangaard Brouer
2026-02-04 17:02 ` [PATCH net-next RFC v1 1/3] net: sched: introduce qdisc-specific drop reason tracing Jesper Dangaard Brouer
2026-02-04 17:03 ` [PATCH net-next RFC v1 2/3] net: sched: sfq: convert to qdisc drop reasons Jesper Dangaard Brouer
2026-02-04 17:03 ` [PATCH net-next RFC v1 3/3] net: sched: sch_cake: use enum qdisc_drop_reason for cobalt_should_drop Jesper Dangaard Brouer
2026-02-05 3:04 ` Jakub Kicinski [this message]
2026-02-05 8:48 ` [PATCH net-next RFC v1 0/3] net: sched: refactor qdisc drop reasons into dedicated tracepoint Jesper Dangaard Brouer
2026-02-05 11:34 ` Toke Høiland-Jørgensen
2026-02-05 14:15 ` Antoine Tenart
2026-02-05 14:46 ` Toke Høiland-Jørgensen
2026-02-05 16:24 ` Antoine Tenart
2026-02-06 14:41 ` Jesper Dangaard Brouer
2026-02-06 15:04 ` Antoine Tenart
2026-02-06 15:21 ` Jesper Dangaard Brouer
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=20260204190417.110f5498@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=carges@cloudflare.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel-team@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@toke.dk \
--cc=xiyou.wangcong@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