From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 95A63C433EF for ; Mon, 23 May 2022 09:28:28 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id A1C266B0005; Mon, 23 May 2022 05:28:27 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 9A54D6B0006; Mon, 23 May 2022 05:28:27 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 86CB76B0007; Mon, 23 May 2022 05:28:27 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 714486B0005 for ; Mon, 23 May 2022 05:28:27 -0400 (EDT) Received: from smtpin21.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 43C2D60FBB for ; Mon, 23 May 2022 09:28:27 +0000 (UTC) X-FDA: 79496482254.21.A5AC058 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by imf22.hostedemail.com (Postfix) with ESMTP id C6FE5C0021 for ; Mon, 23 May 2022 09:28:23 +0000 (UTC) Received: from [2a02:8108:963f:de38:eca4:7d19:f9a2:22c5]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1nt4MF-0007Ub-GJ; Mon, 23 May 2022 11:28:11 +0200 Message-ID: Date: Mon, 23 May 2022 11:28:08 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Content-Language: en-US To: Stefan Wahren , Marcelo Tosatti , Andrew Morton , Nicolas Saenz Julienne Cc: Borislav Petkov , Minchan Kim , Matthew Wilcox , Mel Gorman , Juri Lelli , Thomas Gleixner , Sebastian Andrzej Siewior , "Paul E. McKenney" , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Linux ARM , Phil Elwell , regressions@lists.linux.dev References: <77d6d498-7dd9-03eb-60f2-d7e682bb1b20@i2se.com> From: Thorsten Leemhuis Subject: Re: vchiq: Performance regression since 5.18-rc1 In-Reply-To: <77d6d498-7dd9-03eb-60f2-d7e682bb1b20@i2se.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1653298106;d83b3b70; X-HE-SMSGID: 1nt4MF-0007Ub-GJ X-Rspamd-Server: rspam12 X-Rspamd-Queue-Id: C6FE5C0021 X-Stat-Signature: fmhtipedfnnq1yem8cfij11bsxc7gyfc Authentication-Results: imf22.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf22.hostedemail.com: domain of regressions@leemhuis.info designates 80.237.130.52 as permitted sender) smtp.mailfrom=regressions@leemhuis.info X-Rspam-User: X-HE-Tag: 1653298103-799030 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: [TLDR: I'm adding this regression report to the list of tracked regressions; all text from me you find below is based on a few templates paragraphs you might have encountered already already in similar form.] Hi, this is your Linux kernel regression tracker. On 22.05.22 01:22, Stefan Wahren wrote: > > while testing the staging/vc04_services/interface/vchiq_arm driver with > my Raspberry Pi 3 B+ (multi_v7_defconfig) i noticed a huge performance > regression since [ff042f4a9b050895a42cae893cc01fa2ca81b95c] mm: > lru_cache_disable: replace work queue synchronization with synchronize_rcu > > Usually i run "vchiq_test -f 1" to see the driver is still working [1]. > > Before commit: > > real    0m1,500s > user    0m0,068s > sys    0m0,846s > > After commit: > > real    7m11,449s > user    0m2,049s > sys    0m0,023s Thanks for the report. To be sure below issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression tracking bot: #regzbot ^introduced ff042f4a9b050895a42cae893cc01fa2ca81b95 #regzbot title mm: chiq_test runs 7 minutes instead of ~ 1 second. #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 -- ideally with also telling regzbot about it, as explained here: https://linux-regtracking.leemhuis.info/tracked-regression/ Reminder for developers: When fixing the issue, add 'Link:' tags pointing to the report (the mail this one replied to), as the kernel's documentation call for; above page explains why this is important for tracked regressions. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.