All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jesper Dangaard Brouer <hawk@kernel.org>
Cc: netdev@vger.kernel.org, "Eric Dumazet" <eric.dumazet@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>,
	bpf@vger.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 v4 1/5] net: sched: introduce qdisc-specific drop reason tracing
Date: Tue, 17 Feb 2026 16:34:08 -0800	[thread overview]
Message-ID: <20260217163408.2afc1921@kernel.org> (raw)
In-Reply-To: <177125582938.2500844.3162442443588680144.stgit@firesoul>

On Mon, 16 Feb 2026 16:30:29 +0100 Jesper Dangaard Brouer wrote:
> Create new enum qdisc_drop_reason and trace_qdisc_drop tracepoint
> for qdisc layer drop diagnostics with direct qdisc context visibility.
> 
> The new tracepoint includes qdisc handle, parent, kind (name), and
> device information. Existing SKB_DROP_REASON_QDISC_DROP is retained
> for backwards compatibility via kfree_skb_reason().
> 
> Convert qdiscs with drop reasons to use the new infrastructure.
> 
> Change CAKE's cobalt_should_drop() return type from enum skb_drop_reason
> to enum qdisc_drop_reason to fix implicit enum conversion warnings.
> Use QDISC_DROP_UNSPEC as the 'not dropped' sentinel instead of
> SKB_NOT_DROPPED_YET. Both have the same compiled value (0), so the
> comparison logic remains semantically equivalent.

net/sched/sch_dualpi2.c:594:12: warning: implicit conversion from enumeration type 'enum qdisc_drop_reason' to different enumeration type 'enum skb_drop_reason' [-Wimplicit-enum-enum-cast]
  593 |                         drop_and_retry(q, skb, sch,
      |                         ~~~~~~~~~~~~~~
  594 |                                        QDISC_DROP_CONGESTED);
      |                                        ^~~~~~~~~~~~~~~~~~~~
-- 
pw-bot: cr

  reply	other threads:[~2026-02-18  0:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 15:30 [PATCH net-next v4 0/5] net: sched: refactor qdisc drop reasons into dedicated tracepoint Jesper Dangaard Brouer
2026-02-16 15:30 ` [PATCH net-next v4 1/5] net: sched: introduce qdisc-specific drop reason tracing Jesper Dangaard Brouer
2026-02-18  0:34   ` Jakub Kicinski [this message]
2026-02-16 15:30 ` [PATCH net-next v4 2/5] net: sched: sfq: convert to qdisc drop reasons Jesper Dangaard Brouer
2026-02-16 15:30 ` [PATCH net-next v4 3/5] net: sched: rename QDISC_DROP_FQ_* to generic names Jesper Dangaard Brouer
2026-02-16 15:30 ` [PATCH net-next v4 4/5] net: sched: rename QDISC_DROP_CAKE_FLOOD to QDISC_DROP_FLOOD_PROTECTION Jesper Dangaard Brouer
2026-02-16 15:30 ` [PATCH net-next v4 5/5] net: sched: sch_dualpi2: use qdisc_dequeue_drop() for dequeue drops Jesper Dangaard Brouer

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=20260217163408.2afc1921@kernel.org \
    --to=kuba@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=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 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.