From: Florian Fainelli <florian.fainelli@broadcom.com>
To: netdev@vger.kernel.org
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Justin Chen <justin.chen@broadcom.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
bcm-kernel-feedback-list@broadcom.com (open list:BROADCOM ASP
2.0 ETHERNET DRIVER), linux-kernel@vger.kernel.org (open list)
Subject: [PATCH net-next v2 0/2] net: bcmasp: add support for GRO
Date: Wed, 11 Jun 2025 14:27:28 -0700 [thread overview]
Message-ID: <20250611212730.252342-1-florian.fainelli@broadcom.com> (raw)
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
after:
00:02:35 CPU %usr %nice %sys %iowait %irq %soft %steal
%guest %idle
00:02:36 all 0.25 0.00 1.26 0.00 0.50 7.29 0.00 0.00 90.70
Changes in v2:
- corrected net_device variable in the scope
Florian Fainelli (2):
net: bcmasp: Utilize napi_complete_done() return value
net: bcmasp: enable GRO software interrupt coalescing by default
drivers/net/ethernet/broadcom/asp2/bcmasp_intf.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2025-06-11 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 21:27 Florian Fainelli [this message]
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 ` [PATCH net-next v2 0/2] net: bcmasp: add support for GRO patchwork-bot+netdevbpf
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=20250611212730.252342-1-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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).