From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Antoine Tenart <atenart@redhat.com>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
"Paolo Abeni" <pabeni@redhat.com>,
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: Fri, 6 Feb 2026 16:21:38 +0100 [thread overview]
Message-ID: <007e93e8-ab52-45b3-8e06-107f1b02af0c@kernel.org> (raw)
In-Reply-To: <CADCXZ1wMxCN3B-c+x4SgqC7H-Wap=e_sJ_hu-2B+96b=ip9OVQ@mail.gmail.com>
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
prev parent reply other threads:[~2026-02-06 15:21 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 ` [PATCH net-next RFC v1 0/3] net: sched: refactor qdisc drop reasons into dedicated tracepoint Jakub Kicinski
2026-02-05 8:48 ` 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 [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=007e93e8-ab52-45b3-8e06-107f1b02af0c@kernel.org \
--to=hawk@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=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@redhat.com \
--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