From: patchwork-bot+netdevbpf@kernel.org
To: Mohsin Bashir <mohsin.bashr@gmail.com>
Cc: netdev@vger.kernel.org, alexanderduyck@fb.com, kuba@kernel.org,
kernel-team@meta.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
mike.marciniszyn@gmail.com, lee@trager.us,
jacob.e.keller@intel.com, leitao@debian.org,
vadim.fedorenko@linux.dev, daskald@meta.com,
bobbyeshleman@meta.com, asml.silence@gmail.com
Subject: Re: [PATCH net-next] eth: fbnic: Make Rx completion coalescing configurable
Date: Sat, 12 Sep 2026 00:10:04 +0000 [thread overview]
Message-ID: <178917180464.3171352.16867293381980871719.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260909211111.1795726-1-mohsin.bashr@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 9 Sep 2026 14:11:11 -0700 you wrote:
> From: Mohsin Bashir <hmohsin@meta.com>
>
> The Rx completion queue writeback coalescing window controls how long
> the queue manager may defer writing completions to host memory.
>
> Expose this window through the standard rx-cqe-nsecs ethtool
> parameter. Preserve the existing 2000 ns default and accept values
> from 1000 ns through the device maximum (~109 us).
>
> [...]
Here is the summary with links:
- [net-next] eth: fbnic: Make Rx completion coalescing configurable
https://git.kernel.org/netdev/net-next/c/c0aca269ec07
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:[~2026-09-12 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 21:11 [PATCH net-next] eth: fbnic: Make Rx completion coalescing configurable Mohsin Bashir
2026-09-11 10:19 ` Simon Horman
2026-09-12 0:10 ` 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=178917180464.3171352.16867293381980871719.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=daskald@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=leitao@debian.org \
--cc=mike.marciniszyn@gmail.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vadim.fedorenko@linux.dev \
/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).