From: patchwork-bot+netdevbpf@kernel.org
To: <fan.yu9@zte.com.cn>
Cc: dumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, davem@davemloft.net, jiri@resnulli.us,
xiyou.wangcong@gmail.com, jhs@mojatatu.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
xu.xin16@zte.com.cn, yang.yang29@zte.com.cn,
tu.qiang35@zte.com.cn, jiang.kun2@zte.com.cn,
wang.yaxin@zte.com.cn, qiu.yutan@zte.com.cn,
he.peilin@zte.com.cn
Subject: Re: [PATCH net-next] net/sched: Add precise drop reason for pfifo_fast queue overflows
Date: Fri, 25 Jul 2025 23:26:05 +0000 [thread overview]
Message-ID: <175348596599.3366157.7761382849511498697.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250724212837119BP9HOs0ibXDRWgsXMMir7@zte.com.cn>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 24 Jul 2025 21:28:37 +0800 (CST) you wrote:
> From: Fan Yu <fan.yu9@zte.com.cn>
>
> Currently, packets dropped by pfifo_fast due to queue overflow are
> marked with a generic SKB_DROP_REASON_QDISC_DROP in __dev_xmit_skb().
>
> This patch adds explicit drop reason SKB_DROP_REASON_QDISC_OVERLIMIT
> for queue-full cases, providing better distinction from other qdisc drops.
>
> [...]
Here is the summary with links:
- [net-next] net/sched: Add precise drop reason for pfifo_fast queue overflows
https://git.kernel.org/netdev/net-next/c/bf3c032bfe16
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:[~2025-07-25 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 13:28 [PATCH net-next] net/sched: Add precise drop reason for pfifo_fast queue overflows fan.yu9
2025-07-25 17:25 ` Cong Wang
2025-07-28 9:11 ` fan.yu9
2025-07-28 12:01 ` Simon Horman
2025-07-25 23:26 ` 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=175348596599.3366157.7761382849511498697.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dumazet@google.com \
--cc=fan.yu9@zte.com.cn \
--cc=he.peilin@zte.com.cn \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiang.kun2@zte.com.cn \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qiu.yutan@zte.com.cn \
--cc=tu.qiang35@zte.com.cn \
--cc=wang.yaxin@zte.com.cn \
--cc=xiyou.wangcong@gmail.com \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/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.