From: patchwork-bot+netdevbpf@kernel.org
To: Zak Kemble <zakkemble@gmail.com>
Cc: opendmb@gmail.com, florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: bcmgenet: add support for GRO software interrupt coalescing
Date: Thu, 12 Jun 2025 00:50:36 +0000 [thread overview]
Message-ID: <174968943648.3552664.6839713720894047365.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250610220403.935-1-zakkemble@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Jun 2025 23:04:01 +0100 you wrote:
> Reposting as requested here https://lore.kernel.org/all/20250531224853.1339-1-zakkemble@gmail.com
>
> Hey, these patches enable support for software IRQ coalescing and GRO
> aggregation and applies conservative defaults which can help improve
> system and network performance by reducing the number of hardware
> interrupts and improving GRO aggregation ratio.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: bcmgenet: use napi_complete_done return value
https://git.kernel.org/netdev/net-next/c/28ed9bed5fb2
- [net-next,2/2] net: bcmgenet: enable GRO software interrupt coalescing by default
https://git.kernel.org/netdev/net-next/c/078bb22cfc65
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-06-12 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 22:04 [PATCH net-next 0/2] net: bcmgenet: add support for GRO software interrupt coalescing Zak Kemble
2025-06-10 22:04 ` [PATCH net-next 1/2] net: bcmgenet: use napi_complete_done return value Zak Kemble
2025-06-10 22:04 ` [PATCH net-next 2/2] net: bcmgenet: enable GRO software interrupt coalescing by default Zak Kemble
2025-06-12 0:50 ` 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=174968943648.3552664.6839713720894047365.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.com \
--cc=zakkemble@gmail.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).