Re: Network performance regression with linux 6.1.y. Issue bisected to "5eddb24901ee49eee23c0bfce6af2e83fd5679bd" (gro: add support of (hw)gro packets to gro stack) - Linux kernel regression tracking (#adding)

From: "Linux kernel regression tracking (#adding)"  <regressions@leemhuis.info>
To: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>,
	edumazet@google.com, netdev@vger.kernel.org,
	lixiaoyan@google.com, pabeni@redhat.com, davem@davemloft.net,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: Igor Raits <igor.raits@gooddata.com>
Subject: Re: Network performance regression with linux 6.1.y. Issue bisected to "5eddb24901ee49eee23c0bfce6af2e83fd5679bd" (gro: add support of (hw)gro packets to gro stack)
Date: Fri, 6 Jan 2023 09:36:06 +0100	[thread overview]
Message-ID: <adb0129f-0570-6a11-7ea6-3ee7d851bb50@leemhuis.info> (raw)
In-Reply-To: <CAK8fFZ5pzMaw3U1KXgC_OK4shKGsN=HDcR62cfPOuL0umXE1Ww@mail.gmail.com>

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; all text you find below is based on a few templates
paragraphs you might have encountered already already in similar form.
See link in footer if these mails annoy you.]

[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]

On 05.01.23 18:37, Jaroslav Pulchart wrote:
> Hello,
> 
> I would like to report a 6.1,y regression in a network performance
> observed when using "git clone".
> 
> BAD: "git clone" speed with kernel 6.1,y:
>    # git clone git@github.com:..../.....git
>    ...
>    Receiving objects:   8% (47797/571306), 20.69 MiB | 3.27 MiB/s
> 
> GOOD: "git clone" speed with kernel 6.0,y:
>    # git clone git@github.com:..../.....git
>    ...
>    Receiving objects:  72% (411341/571306), 181.05 MiB | 60.27 MiB/s
> 
> I bisected the issue to a commit
> 5eddb24901ee49eee23c0bfce6af2e83fd5679bd "gro: add support of (hw)gro
> packets to gro stack". Reverting it from 6.1.y branch makes the git
> clone fast like with 6.0.y.

Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:

#regzbot ^introduced 5eddb24901ee49eee23c0bfce6af2e83fd5679bd
#regzbot title net: gro: Network performance regressed
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (see page linked in footer for details).

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.