linux-kernel - Re: [PATCH v1 0/2] net: bcmgenet: add support for GRO software interrupt coalescing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <44cec5e4-2eaa-498f-9852-401a4a97fab1@broadcom.com>
Date: Mon, 9 Jun 2025 14:10:49 -0700
From: Florian Fainelli <florian.fainelli@...adcom.com>
To: Zak Kemble <zakkemble@...il.com>, Doug Berger <opendmb@...il.com>,
 Florian Fainelli <florian.fainelli@...adcom.com>,
 Broadcom internal kernel review list
 <bcm-kernel-feedback-list@...adcom.com>, Andrew Lunn
 <andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>,
 Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
 Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 0/2] net: bcmgenet: add support for GRO software
 interrupt coalescing

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