From: patchwork-bot+netdevbpf@kernel.org
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: netdev@vger.kernel.org, justin.chen@broadcom.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: bcmasp: add support for GRO
Date: Fri, 13 Jun 2025 01:30:42 +0000 [thread overview]
Message-ID: <174977824248.179245.828577192312003957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250611212730.252342-1-florian.fainelli@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 Jun 2025 14:27:28 -0700 you wrote:
> These two patches add support for GRO software interrupt coalescing,
> kudos to Zak for doing this on bcmgenet first.
>
> before:
>
> 00:03:31 CPU %usr %nice %sys %iowait %irq %soft %steal
> %guest %idle
> 00:03:32 all 0.00 0.00 1.51 0.00 0.50 7.29 0.00 0.00 90.70
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: bcmasp: Utilize napi_complete_done() return value
https://git.kernel.org/netdev/net-next/c/391859cb17f5
- [net-next,v2,2/2] net: bcmasp: enable GRO software interrupt coalescing by default
https://git.kernel.org/netdev/net-next/c/b0f5b1682957
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-13 1:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 21:27 [PATCH net-next v2 0/2] net: bcmasp: add support for GRO Florian Fainelli
2025-06-11 21:27 ` [PATCH net-next v2 1/2] net: bcmasp: Utilize napi_complete_done() return value Florian Fainelli
2025-06-12 20:22 ` Joe Damato
2025-06-11 21:27 ` [PATCH net-next v2 2/2] net: bcmasp: enable GRO software interrupt coalescing by default Florian Fainelli
2025-06-12 20:33 ` Joe Damato
2025-06-13 1: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=174977824248.179245.828577192312003957.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=justin.chen@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).