From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Cc: nic_swsd@realtek.com, netdev@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: Performance Regression due to ASPM disable patch
Date: Tue, 25 Jul 2023 15:43:27 +0200 [thread overview]
Message-ID: <2d2d2225-3a64-2255-92c8-3237402e3f3d@leemhuis.info> (raw)
In-Reply-To: <425eba3b-0138-81d1-f615-97fc24b2d51d@leemhuis.info>
[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.
prev parent reply other threads:[~2023-07-25 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230712155834epcas5p1140d90c8a0a181930956622728c4dd89@epcas5p1.samsung.com>
2023-07-12 15:55 ` Performance Regression due to ASPM disable patch Anuj Gupta
2023-07-13 5:59 ` Heiner Kallweit
2023-07-13 12:49 ` Anuj Gupta
2023-07-13 12:37 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-07-25 13:43 ` Linux regression tracking #update (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=2d2d2225-3a64-2255-92c8-3237402e3f3d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-nvme@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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).