Re: [PATCH net-next RFC v1 0/3] net: sched: refactor qdisc drop reasons into dedicated tracepoint

[Jesper Dangaard Brouer <hawk@kernel.org>]

On 05/02/2026 17.24, Antoine Tenart wrote:
> On Thu, Feb 05, 2026 at 03:46:29PM +0100, Toke Høiland-Jørgensen wrote:
>> Antoine Tenart <atenart@redhat.com> writes:
>>
>>> I'm wondering why not using the drop reason subsys logic to combine the
>>> qdisc specific enum while not conflicting with drop reasons and allowing
>>> to inject the qdisc reasons into drop reason enabled helpers as well?
>>
>> See this prior discussion for how the proposal came to be:
>>
>> https://lore.kernel.org/all/6be17a08-f8aa-4f91-9bd0-d9e1f0a92d90@kernel.org/
>>
>> Basically, figuring out which qdisc a drop came from is not possible
>> with the current drop_reason code.
>>
>> So it's not just new drop reasons, it's a separate tracepoint with more
>> information available (qdisc handle, name, etc). So you'll get two
>> events for qdisc drops with this series (from patch 1):
>>
>> +		trace_qdisc_drop(q, txq, dev, skb, reason);
>> +		kfree_skb_reason(skb, SKB_DROP_REASON_QDISC_DROP);
> 
> Right and that's fine. Using the drop reason subsys logic you could turn
> the above into:
> 
>   +		trace_qdisc_drop(q, txq, dev, skb, reason);
>   +		kfree_skb_reason(skb, (u32)reason);
> 
> You can look at enum skb_drop_reason_subsys and how that is used within
> OvS (net/openvswitch/drop.h) for example.
> 

Thanks for the input Antoine, I've adapted V2 to use skb_drop_reason_subsys.

Can you point me at the OVS userspace code that consume these subsys 
drop_reason's?

--Jesper
[V2] 
https://lore.kernel.org/all/177032644012.1975497.16411100029657607833.stgit@firesoul/