From: patchwork-bot+netdevbpf@kernel.org
To: Bryam Vargas <hexlabsecurity@proton.me>
Cc: vinicius.gomes@intel.com, pabeni@redhat.com, jhs@mojatatu.com,
jiri@resnulli.us, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, netdev@vger.kernel.org,
jarkao2@gmail.com, vladimir.oltean@nxp.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] net/sched: finish the qdisc_dequeue_peeked conversion (taprio, multiq)
Date: Sat, 27 Jun 2026 02:00:25 +0000 [thread overview]
Message-ID: <178252562506.1167656.8248831428302845030.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260625-b4-disp-31bcb279-v1-0-85c40b83c529@proton.me>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 25 Jun 2026 04:51:18 -0500 you wrote:
> Commit 77be155cba4e added peek emulation: a non-work-conserving qdisc's
> ->peek dequeues one skb and stashes it in the child's gso_skb. A parent
> that peeks such a child must then take the packet with
> qdisc_dequeue_peeked(), not a direct ->dequeue(), or the stashed skb is
> bypassed and the child's qlen/backlog desync. sch_red and sch_sfb were
> just fixed for this; taprio and multiq still take the direct path.
>
> [...]
Here is the summary with links:
- [1/2] net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked
https://git.kernel.org/netdev/net/c/e056e1dfcddc
- [2/2] net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked
https://git.kernel.org/netdev/net/c/54f6b0c843e2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-27 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 9:51 [PATCH 0/2] net/sched: finish the qdisc_dequeue_peeked conversion (taprio, multiq) Bryam Vargas via B4 Relay
2026-06-25 9:51 ` [PATCH 1/2] net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked Bryam Vargas via B4 Relay
2026-06-26 17:16 ` Victor Nogueira
2026-06-26 17:46 ` Jamal Hadi Salim
2026-06-25 9:51 ` [PATCH 2/2] net/sched: sch_multiq: " Bryam Vargas via B4 Relay
2026-06-26 17:18 ` Victor Nogueira
2026-06-26 17:47 ` Jamal Hadi Salim
2026-06-27 2:00 ` patchwork-bot+netdevbpf [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=178252562506.1167656.8248831428302845030.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hexlabsecurity@proton.me \
--cc=horms@kernel.org \
--cc=jarkao2@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.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