From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Zak Kemble <zakkemble@gmail.com>, Doug Berger <opendmb@gmail.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@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>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] net: bcmgenet: add support for GRO software interrupt coalescing
Date: Mon, 9 Jun 2025 14:10:49 -0700 [thread overview]
Message-ID: <44cec5e4-2eaa-498f-9852-401a4a97fab1@broadcom.com> (raw)
In-Reply-To: <20250609210809.1006-1-zakkemble@gmail.com>
Hi Zak,
On 6/9/25 14:08, Zak Kemble 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.
Since I gave you Tested-by and Reviewed-by tags, you should have been
amending your commits with such tags, also you should be specifying the
tree you are targeting, in that case it is "net-next", so the patches
should be:
[PATCH net-next 0/2]
[PATCH net-next 1/2] ...
[PATCH net-next 2/2] ...
etc.
Please wait 24hrs before reposting an updated version with the tags and
proper prefixing, thanks!
--
Florian
next prev parent reply other threads:[~2025-06-09 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 21:08 Zak Kemble
2025-06-09 21:08 ` [PATCH v1 1/2] net: bcmgenet: use napi_complete_done return value Zak Kemble
2025-06-09 21:08 ` [PATCH v1 2/2] net: bcmgenet: enable GRO software interrupt coalescing by default Zak Kemble
2025-06-09 21:10 ` Florian Fainelli [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-31 22:48 [PATCH v1 0/2] net: bcmgenet: add support for GRO software interrupt coalescing Zak Kemble
2025-06-02 19:00 ` Florian Fainelli
2025-06-09 20:35 ` Florian Fainelli
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=44cec5e4-2eaa-498f-9852-401a4a97fab1@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=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
all inboxes | Powered by JetHome®