public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <hawk@kernel.org>
To: "Paolo Abeni" <pabeni@redhat.com>,
	netdev@vger.kernel.org, "Eric Dumazet" <eric.dumazet@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bpf@vger.kernel.org, Jakub Kicinski <kuba@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 v3 1/6] net: sched: introduce qdisc-specific drop reason tracing
Date: Fri, 13 Feb 2026 18:50:09 +0100	[thread overview]
Message-ID: <25d8d1ab-b01c-4416-9f8d-9f29e59dc781@kernel.org> (raw)
In-Reply-To: <dda23104-3ca9-4f81-aa79-b0517a9cc5a2@redhat.com>



On 11/02/2026 09.46, Paolo Abeni wrote:
> On 2/11/26 9:36 AM, Paolo Abeni wrote:
>> On 2/6/26 5:24 PM, Jesper Dangaard Brouer wrote:
>>> @@ -593,7 +591,7 @@ static struct sk_buff *dualpi2_qdisc_dequeue(struct Qdisc *sch)
>>>   	while ((skb = dequeue_packet(sch, q, &credit_change, now))) {
>>>   		if (!q->drop_early && must_drop(sch, q, skb)) {
>>>   			drop_and_retry(q, skb, sch,
>>> -				       SKB_DROP_REASON_QDISC_CONGESTED);
>>> +				       QDISC_DROP_CONGESTED);
>>
>> An explicit cast is needed above to avoid compiler warning (or you can
>> change drop_and_retry() signature).
> 
> I see that the type confusion issues are handled for good by later
> patches in the series, but I still think it would be better to avoid
> introducing them with explicit casts as needed (removed by later patches).
> 
>> Also a few lines below there is another drop_and_retry() calls that is
>> not converted.
> 
> I see it's handled by a later patch. I guess it would be useful to
> mention such fact in the commit message.

Yes, this is handled in patch 3/6.  I acknowledge this is annoying from
a review perspective, and also wrong because I'm leaving compiler
warning that I'm fixing up later.  The reason for splitting it out into
a separate patch was because I wanted document (in commit desc) the
special usage of SKB_NOT_DROPPED_YET as a sentinel value.

I'm leaning towards folding patch 3 into this patch 1, as suggested by Toke.

--Jesper

  reply	other threads:[~2026-02-13 17:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 16:24 [PATCH net-next v3 0/6] net: sched: refactor qdisc drop reasons into dedicated tracepoint Jesper Dangaard Brouer
2026-02-06 16:24 ` [PATCH net-next v3 1/6] net: sched: introduce qdisc-specific drop reason tracing Jesper Dangaard Brouer
2026-02-10 11:47   ` Toke Høiland-Jørgensen
2026-02-11  8:36   ` Paolo Abeni
2026-02-11  8:46     ` Paolo Abeni
2026-02-13 17:50       ` Jesper Dangaard Brouer [this message]
2026-02-11  8:50   ` Paolo Abeni
2026-02-06 16:24 ` [PATCH net-next v3 2/6] net: sched: sfq: convert to qdisc drop reasons Jesper Dangaard Brouer
2026-02-10 11:48   ` Toke Høiland-Jørgensen
2026-02-06 16:24 ` [PATCH net-next v3 3/6] net: sched: sch_cake: use enum qdisc_drop_reason for cobalt_should_drop Jesper Dangaard Brouer
2026-02-10 11:52   ` Toke Høiland-Jørgensen
2026-02-06 16:24 ` [PATCH net-next v3 4/6] net: sched: rename QDISC_DROP_CAKE_FLOOD to QDISC_DROP_FLOOD_PROTECTION Jesper Dangaard Brouer
2026-02-10 11:53   ` Toke Høiland-Jørgensen
2026-02-06 16:24 ` [PATCH net-next v3 5/6] net: sched: rename QDISC_DROP_FQ_* to generic names Jesper Dangaard Brouer
2026-02-10 11:54   ` Toke Høiland-Jørgensen
2026-02-06 16:24 ` [PATCH net-next v3 6/6] net: sched: sch_dualpi2: use qdisc_dequeue_drop() for dequeue drops Jesper Dangaard Brouer
2026-02-10 12:00   ` Toke Høiland-Jørgensen

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=25d8d1ab-b01c-4416-9f8d-9f29e59dc781@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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox