[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <007e93e8-ab52-45b3-8e06-107f1b02af0c@kernel.org>
Date: Fri, 6 Feb 2026 16:21:38 +0100
From: Jesper Dangaard Brouer <hawk@...nel.org>
To: Antoine Tenart <atenart@...hat.com>
Cc: Toke Høiland-Jørgensen <toke@...hat.com>,
Jakub Kicinski <kuba@...nel.org>, Eric Dumazet <eric.dumazet@...il.com>,
netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>, bpf@...r.kernel.org, horms@...nel.org,
jiri@...nulli.us, edumazet@...gle.com, xiyou.wangcong@...il.com,
jhs@...atatu.com, carges@...udflare.com, kernel-team@...udflare.com
Subject: Re: [PATCH net-next RFC v1 0/3] net: sched: refactor qdisc drop
reasons into dedicated tracepoint
On 06/02/2026 16.04, Antoine Tenart wrote:
> On Fri, Feb 06, 2026 at 03:41:23PM +0100, Jesper Dangaard Brouer wrote:
>> On 05/02/2026 17.24, Antoine Tenart wrote:
>>
>> Can you point me at the OVS userspace code that consume these subsys
>> drop_reason's?
>
> I think this was mostly added for debugging utilities and not consumed
> by OvS directly but I don't know the OvS userspace code tbf. Anything
> you're looking for specifically?
>
I'm just trying to making sure that I/we don't break any userspace code.
Yes, looks like debugging tools are the consumer. E.g. The Red Hat
NetObserv[1] tool mentions OVS decoding drop reason.
[1]
https://www.redhat.com/en/blog/network-observability-real-time-per-flow-packets-drop
--Jesper
Powered by blists - more mailing lists