On Thu, May 07, 2026 at 12:59:29PM +0000, Ciara Loftus wrote:
> From: Mukul Katiyar <[email protected]>
>
> When a TM hierarchy is fully deleted and then committed, the hardware
> scheduler nodes may be left with any bandwidth limits that were
> programmed by the previous hierarchy commit. These stale limits may
> remain in effect the next time the device starts, permanently throttling
> traffic even though the TM hierarchy was removed.
>
> Fix this by resetting all descendant hardware scheduler nodes to their
> default state when committing an empty hierarchy. Also restore the port
> queue count to its hardware default and clear the committed flag so the
> port starts cleanly without any TM configuration applied.
>
> Fixes: 715d449a965b ("net/ice: enhance Tx scheduler hierarchy support")
> Cc: [email protected]
>
> Signed-off-by: Mukul Katiyar <[email protected]>
> Signed-off-by: Ciara Loftus <[email protected]>
> ---
> v2:
> * Ensure restore is only performed if a hierarchy has already been
> committed
> ---
> .mailmap | 1 +
> drivers/net/intel/ice/ice_tm.c | 24 ++++++++++++++++++++++--
> 2 files changed, 23 insertions(+), 2 deletions(-)
Acked-by: Bruce Richardson <[email protected]>
