From: "Linux kernel regression tracking (Thorsten Leemhuis)" <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: Mon, 30 Jan 2023 13:55:57 +0100 [thread overview]
Message-ID: <f7e7da82-2050-1866-e5b4-b7e9ea778b89@leemhuis.info> (raw)
In-Reply-To: <adb0129f-0570-6a11-7ea6-3ee7d851bb50@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 06.01.23 09:36, Linux kernel regression tracking (#adding) wrote:
> 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
#regzbot fix: 7871f54e3dee
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.
#regzbot ignore-activity
prev parent reply other threads:[~2023-01-30 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 17:37 Network performance regression with linux 6.1.y. Issue bisected to "5eddb24901ee49eee23c0bfce6af2e83fd5679bd" (gro: add support of (hw)gro packets to gro stack) Jaroslav Pulchart
2023-01-05 17:43 ` Eric Dumazet
2023-01-05 17:54 ` Jaroslav Pulchart
2023-01-05 18:49 ` Eric Dumazet
2023-01-05 19:56 ` Jaroslav Pulchart
2023-01-06 14:04 ` Eric Dumazet
2023-01-06 15:04 ` Jaroslav Pulchart
2023-01-06 8:36 ` Linux kernel regression tracking (#adding)
2023-01-30 12:55 ` Linux kernel regression tracking (Thorsten Leemhuis) [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=f7e7da82-2050-1866-e5b4-b7e9ea778b89@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=igor.raits@gooddata.com \
--cc=jaroslav.pulchart@gooddata.com \
--cc=lixiaoyan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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).