From: patchwork-bot+netdevbpf@kernel.org
To: Jesper Dangaard Brouer <hawk@kernel.org>
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com,
davem@davemloft.net, pabeni@redhat.com, toke@toke.dk,
bpf@vger.kernel.org, kuba@kernel.org, horms@kernel.org,
jiri@resnulli.us, edumazet@google.com, xiyou.wangcong@gmail.com,
jhs@mojatatu.com, atenart@redhat.com, carges@cloudflare.com,
kernel-team@cloudflare.com
Subject: Re: [PATCH net-next v5 0/5] net: sched: refactor qdisc drop reasons into dedicated tracepoint
Date: Sun, 01 Mar 2026 00:00:12 +0000 [thread overview]
Message-ID: <177232321230.3162700.9839449465077142615.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <177211325634.3011628.9343837509740374154.stgit@firesoul>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 26 Feb 2026 14:44:06 +0100 you wrote:
> 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.
>
> Background:
> -----------
> Identifying which qdisc dropped a packet via skb_drop_reason is difficult.
> Normally, the kfree_skb tracepoint caller "location" hints at the dropping
> code, but qdisc drops happen at a central point (__dev_queue_xmit), making
> this unusable. As a workaround, commits 5765c7f6e317 ("net_sched: sch_fq:
> add three drop_reason") and a42d71e322a8 ("net_sched: sch_cake: Add drop
> reasons") encoded qdisc names directly in the drop reason enums.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/5] net: sched: introduce qdisc-specific drop reason tracing
https://git.kernel.org/netdev/net-next/c/ff2998f29f39
- [net-next,v5,2/5] net: sched: sfq: convert to qdisc drop reasons
https://git.kernel.org/netdev/net-next/c/3e28f8ad478f
- [net-next,v5,3/5] net: sched: rename QDISC_DROP_FQ_* to generic names
https://git.kernel.org/netdev/net-next/c/f30d9073ec19
- [net-next,v5,4/5] net: sched: rename QDISC_DROP_CAKE_FLOOD to QDISC_DROP_FLOOD_PROTECTION
https://git.kernel.org/netdev/net-next/c/9d3e7f971898
- [net-next,v5,5/5] net: sched: sch_dualpi2: use qdisc_dequeue_drop() for dequeue drops
https://git.kernel.org/netdev/net-next/c/67713dff6398
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-01 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 13:44 [PATCH net-next v5 0/5] net: sched: refactor qdisc drop reasons into dedicated tracepoint Jesper Dangaard Brouer
2026-02-26 13:44 ` [PATCH net-next v5 1/5] net: sched: introduce qdisc-specific drop reason tracing Jesper Dangaard Brouer
2026-02-26 13:44 ` [PATCH net-next v5 2/5] net: sched: sfq: convert to qdisc drop reasons Jesper Dangaard Brouer
2026-02-26 13:44 ` [PATCH net-next v5 3/5] net: sched: rename QDISC_DROP_FQ_* to generic names Jesper Dangaard Brouer
2026-02-26 13:44 ` [PATCH net-next v5 4/5] net: sched: rename QDISC_DROP_CAKE_FLOOD to QDISC_DROP_FLOOD_PROTECTION Jesper Dangaard Brouer
2026-02-26 13:45 ` [PATCH net-next v5 5/5] net: sched: sch_dualpi2: use qdisc_dequeue_drop() for dequeue drops Jesper Dangaard Brouer
2026-03-01 0:00 ` patchwork-bot+netdevbpf [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=177232321230.3162700.9839449465077142615.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=atenart@redhat.com \
--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=kuba@kernel.org \
--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