From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Liam R. Howlett" <Liam.Howlett@Oracle.com>,
Bagas Sanjaya <bagasdotme@gmail.com>, Chun Ng <chunn@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Ankita Garg <ankitag@nvidia.com>,
Suren Baghdasaryan <surenb@google.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: Re: [REGRESSION]: mmap performance regression starting with k-6.1
Date: Fri, 24 Nov 2023 06:08:24 +0100 [thread overview]
Message-ID: <2541055a-48c9-4680-ad9b-5a3c41995a1d@leemhuis.info> (raw)
In-Reply-To: <20231123143452.erzar3sqhg37hjxz@revolver>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 23.11.23 15:34, Liam R. Howlett wrote:
> * Bagas Sanjaya <bagasdotme@gmail.com> [231123 00:07]:
>> On Wed, Nov 22, 2023 at 08:03:19PM +0000, Chun Ng wrote:
>>>
>>> Recently I observed there is performance regression on system call mmap(..). I tried both vanilla kernels and Raspberry Pi kernels on a Raspberry Pi 4 box and the results are pretty consistent among them.
>>>
>>> Bisection showed that the regression starts from k-6.1, and the latest vanilla k-6.7 is still showing the same regression.
>
> This is almost certainly the maple tree. The tree is slower on writes
> than the rbtree and so if the benchmark mmaps/munmaps in a tight loop
> you will see this slow down. [...]
>
>> Anyway, I'm adding this regression to regzbot:
>> #regzbot ^introduced: v6.0..v6.1
Liam, many thx for your reply. I known that you are still working on
optimizing things in this area again, so I don't think this is worth
tracking this as a regression: that doesn't buy us much afaics. And it
might not be a regression at all anyway (not totally sure, didn't look
into the details due to the former aspect; sounded a bit like the
problem only can be seen in a microbenchmark; whatever).
#regzbot resolve: not worth tracking
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
If I did something stupid, please tell me, as explained on that page.
next prev parent reply other threads:[~2023-11-24 5:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 20:03 Chun Ng
2023-11-23 1:18 ` Bagas Sanjaya
2023-11-23 3:06 ` Chun Ng
2023-11-23 5:01 ` Bagas Sanjaya
2023-11-23 5:07 ` Bagas Sanjaya
2023-11-23 14:34 ` Liam R. Howlett
2023-11-24 5:08 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
[not found] ` <20231126071854.19490-1-00107082@163.com>
2023-11-26 13:47 ` Matthew Wilcox
2023-11-23 15:38 ` Matthew Wilcox
2023-11-24 0:15 ` Bagas Sanjaya
2023-11-24 1:04 ` Matthew Wilcox
2023-11-24 11:52 ` Greg KH
2023-11-24 15:06 ` Matthew Wilcox
2023-11-24 15:13 ` Greg KH
2023-11-24 15:29 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-25 1:50 ` Chun Ng
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=2541055a-48c9-4680-ad9b-5a3c41995a1d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ankitag@nvidia.com \
--cc=bagasdotme@gmail.com \
--cc=chunn@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=regressions@lists.linux.dev \
--cc=surenb@google.com \
--cc=willy@infradead.org \
/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