From: patchwork-bot+netdevbpf@kernel.org
To: Mohsin Bashir <mohsin.bashr@gmail.com>
Cc: netdev@vger.kernel.org, alexanderduyck@fb.com,
almasrymina@google.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
kernel-team@meta.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
pabeni@redhat.com, rmk+kernel@armlinux.org.uk
Subject: Re: [PATCH net-next V2] eth: fbnic: Configure RDE settings for pause frame
Date: Tue, 18 Nov 2025 01:00:14 +0000 [thread overview]
Message-ID: <176342761424.3532963.7569003490275374200.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251113232610.1151712-1-mohsin.bashr@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 13 Nov 2025 15:26:10 -0800 you wrote:
> fbnic supports pause frames. When pause frames are enabled presumably
> user expects lossless operation from the NIC. Make sure we configure
> RDE (Rx DMA Engine) to DROP_NEVER mode to avoid discards due to delays
> in fetching Rx descriptors from the host.
>
> While at it enable DROP_NEVER when NIC only has a single queue
> configured. In this case the NIC acts as a FIFO so there's no risk
> of head-of-line blocking other queues by making RDE wait. If pause
> is disabled this just moves the packet loss from the DMA engine to
> the Rx buffer.
>
> [...]
Here is the summary with links:
- [net-next,V2] eth: fbnic: Configure RDE settings for pause frame
https://git.kernel.org/netdev/net-next/c/0135333914d6
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:[~2025-11-18 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 23:26 [PATCH net-next V2] eth: fbnic: Configure RDE settings for pause frame Mohsin Bashir
2025-11-15 20:21 ` Andrew Lunn
2025-11-18 1:00 ` 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=176342761424.3532963.7569003490275374200.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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