[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2d2d2225-3a64-2255-92c8-3237402e3f3d@leemhuis.info>
Date: Tue, 25 Jul 2023 15:43:27 +0200
From: "Linux regression tracking #update (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Linux kernel regressions list <regressions@...ts.linux.dev>
Cc: nic_swsd@...ltek.com, netdev@...r.kernel.org,
linux-nvme@...ts.infradead.org
Subject: Re: Performance Regression due to ASPM disable patch
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 13.07.23 14:37, Linux regression tracking #adding (Thorsten Leemhuis)
wrote:
> On 12.07.23 17:55, Anuj Gupta wrote:
>>
>> I see a performance regression for read/write workloads on our NVMe over
>> fabrics using TCP as transport setup.
>> IOPS drop by 23% for 4k-randread [1] and by 18% for 4k-randwrite [2].
>
> #regzbot ^introduced e1ed3e4d91112027b90c7ee61479141b3f94
> #regzbot title net: r8169: performance regression for read/write
> workloads on our NVMe over fabrics
> #regzbot ignore-activity
The fix did not properly link to the report (it only linked to a reply
in the thread), hence regzbot missed it:
#regzbot fix: e31a9fedc7d8d8
#regzbot ignore-activity
/me meanwhile wonders if it'S worth teaching regzbot how to handle these
cases
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.
Powered by blists - more mailing lists