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,
ndabilpuram@marvell.com
Subject: Re: [net PATCH] octeontx2-af: Always configure NIX TX link credits based on max frame size
Date: Thu, 04 Jan 2024 10:40:24 +0000 [thread overview]
Message-ID: <170436482487.2302.15098697644202320061.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240102095643.25296-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 15:26:43 +0530 you wrote:
> Currently the NIX TX link credits are initialized based on the max frame
> size that can be transmitted on a link but when the MTU is changed, the
> NIX TX link credits are reprogrammed by the SW based on the new MTU value.
> Since SMQ max packet length is programmed to max frame size by default,
> there is a chance that NIX TX may stall while sending a max frame sized
> packet on the link with insufficient credits to send the packet all at
> once. This patch avoids stall issue by not changing the link credits
> dynamically when the MTU is changed.
>
> [...]
Here is the summary with links:
- [net] octeontx2-af: Always configure NIX TX link credits based on max frame size
https://git.kernel.org/netdev/net/c/a0d9528f6daf
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 9:56 [net PATCH] octeontx2-af: Always configure NIX TX link credits based on max frame size 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=170436482487.2302.15098697644202320061.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=ndabilpuram@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