All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: davem@davemloft.net, hkelam@marvell.com,
	linux-kernel@vger.kernel.org, naveenm@marvell.com,
	netdev@vger.kernel.org, sgoutham@marvell.com,
	andrew+netdev@lunn.ch, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com
Subject: Re: [PATCH v4 net] octeontx2-pf: reset HTB scheduler topology before freeing queues
Date: Thu, 10 Sep 2026 01:40:05 +0000	[thread overview]
Message-ID: <178900440563.1145188.13874593084927115417.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260903020533.3068041-1-rkannoth@marvell.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 3 Sep 2026 07:35:33 +0530 you wrote:
> HTB offload programs NIX_AF_TLxX_TOPOLOGY on QoS-allocated scheduler
> queues via otx2_qos_txschq_set_parent_topology(), but teardown freed
> those queues without clearing TOPOLOGY.  The AF only restores PARENT and
> SCHEDULE on free, so PRIO_ANCHOR/RR_PRIO settings can survive in the
> shared scheduler pool and affect later allocations.
> 
> Add otx2_qos_reset_schq_topology() and otx2_qos_free_hw_schq() to zero
> TL4 through TL2 TOPOLOGY before each schq is returned to the AF during
> hierarchy teardown and cfg rollback.  Skip the aggregation level (TL1):
> it is a per-tx-link queue shared by the PF, default Tx hierarchy and VFs,
> and is not freed back to the AF by nix_txschq_free_one().
> 
> [...]

Here is the summary with links:
  - [v4,net] octeontx2-pf: reset HTB scheduler topology before freeing queues
    https://git.kernel.org/netdev/net/c/ef39fca85085

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-10  1:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  2:05 [PATCH v4 net] octeontx2-pf: reset HTB scheduler topology before freeing queues Ratheesh Kannoth
2026-09-08 17:07 ` netdev-bot+sashiko
2026-09-09  3:17   ` Ratheesh Kannoth
2026-09-09  6:57     ` Simon Horman
2026-09-10  1:40 ` 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=178900440563.1145188.13874593084927115417.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkelam@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveenm@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=sgoutham@marvell.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.