public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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,
	lcherian@marvell.com, gakula@marvell.com, hkelam@marvell.com,
	sbhatta@marvell.com
Subject: Re: [net PATCH] octeontx2-af: Modify SMQ flush sequence to drop packets
Date: Tue, 10 Sep 2024 10:30:28 +0000	[thread overview]
Message-ID: <172596422829.208623.12220342892679054459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240906045838.1620308-1-naveenm@marvell.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 6 Sep 2024 10:28:38 +0530 you wrote:
> The current implementation of SMQ flush sequence waits for the packets
> in the TM pipeline to be transmitted out of the link. This sequence
> doesn't succeed in HW when there is any issue with link such as lack of
> link credits, link down or any other traffic that is fully occupying the
> link bandwidth (QoS). This patch modifies the SMQ flush sequence to
> drop the packets after TL1 level (SQM) instead of polling for the packets
> to be sent out of RPM/CGX link.
> 
> [...]

Here is the summary with links:
  - [net] octeontx2-af: Modify SMQ flush sequence to drop packets
    https://git.kernel.org/netdev/net/c/019aba04f08c

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



      reply	other threads:[~2024-09-10 10:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06  4:58 [net PATCH] octeontx2-af: Modify SMQ flush sequence to drop packets Naveen Mamindlapalli
2024-09-10 10:30 ` 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=172596422829.208623.12220342892679054459.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=kuba@kernel.org \
    --cc=lcherian@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveenm@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sbhatta@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox