From: patchwork-bot+netdevbpf@kernel.org
To: Naveen Mamindlapalli <naveenm@marvell.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, sgoutham@marvell.com
Subject: Re: [net PATCH] octeontx2-af: Re-enable MAC TX in otx2_stop processing
Date: Thu, 04 Jan 2024 10:40:24 +0000 [thread overview]
Message-ID: <170436482482.2302.13087234357277390960.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240102141400.9146-1-naveenm@marvell.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 2 Jan 2024 19:44:00 +0530 you wrote:
> During QoS scheduling testing with multiple strict priority flows, the
> netdev tx watchdog timeout routine is invoked when a low priority QoS
> queue doesn't get a chance to transmit the packets because other high
> priority flows are completely subscribing the transmit link. The netdev
> tx watchdog timeout routine will stop MAC RX and TX functionality in
> otx2_stop() routine before cleanup of HW TX queues which results in SMQ
> flush errors because the packets belonging to low priority queues will
> never gets flushed since MAC TX is disabled. This patch fixes the issue
> by re-enabling MAC TX to ensure the packets in HW pipeline gets flushed
> properly.
>
> [...]
Here is the summary with links:
- [net] octeontx2-af: Re-enable MAC TX in otx2_stop processing
https://git.kernel.org/netdev/net/c/818ed8933bd1
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:[~2024-01-04 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 14:14 [net PATCH] octeontx2-af: Re-enable MAC TX in otx2_stop processing Naveen Mamindlapalli
2024-01-04 10: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=170436482482.2302.13087234357277390960.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).