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 F1309C4321E for ; Tue, 29 Nov 2022 13:46:58 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 7EB2D6B0078; Tue, 29 Nov 2022 08:46:58 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 79C356B007D; Tue, 29 Nov 2022 08:46:58 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 664026B007E; Tue, 29 Nov 2022 08:46:58 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 5634A6B0078 for ; Tue, 29 Nov 2022 08:46:58 -0500 (EST) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 237F71C678A for ; Tue, 29 Nov 2022 08:59:44 +0000 (UTC) X-FDA: 80185881888.11.7E3AB2D Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by imf11.hostedemail.com (Postfix) with ESMTP id 7DB7A4000E for ; Tue, 29 Nov 2022 08:59:43 +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 1ozwSr-0007IJ-OX; Tue, 29 Nov 2022 09:59:41 +0100 Message-ID: <84964891-5a39-adb2-3093-54b716ca94ae@leemhuis.info> Date: Tue, 29 Nov 2022 09:59:39 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.1 Subject: Re: [mm] f35b5d7d67: will-it-scale.per_process_ops -95.5% regression #forregzbot Content-Language: en-US, de-DE To: "regressions@lists.linux.dev" Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org References: <202210181535.7144dd15-yujie.liu@intel.com> <87edv4r2ip.fsf@yhuang6-desk2.ccr.corp.intel.com> From: Thorsten Leemhuis In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1669712383;640b2789; X-HE-SMSGID: 1ozwSr-0007IJ-OX ARC-Authentication-Results: i=1; imf11.hostedemail.com; dkim=none; spf=pass (imf11.hostedemail.com: domain of regressions@leemhuis.info designates 80.237.130.52 as permitted sender) smtp.mailfrom=regressions@leemhuis.info; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1669712383; a=rsa-sha256; cv=none; b=svuJNMwvaAKFIwHGFLIf0JojTDfhZaIU1bBPFZkbaSTZjnAr2qOR3h0G2uJZ3uIUD/UQ0P XixBwwSDKyCle3gGxyeXIhuLGGkZ5J+LyGowuxzSdWfnX2O+FK8se0nNx6BWpGUbfESQHH 8hZfFXvSKcIJx8vsZmG3zQtN+62u3B4= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1669712383; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fpS0Xn2xXG17BLT3GnLdN6qU/+pXn01QIkhfARLE6+c=; b=F1SzQTOQtVN5p6EL6SMXLfszr8HJEAeyIXQL3OKc+nLorRprM6WK2cT1Ey5jWNp0v4wTsp hCvDKIeqankJ8nDhu1QNgapUuyCJ1bXrUQrFmRsO/eUczF8xLd5j7MdhYIuPOTQvbrncCJ d5pJ6fA5dAK/2f3ed1oN9u7eZI5Ohp0= X-Rspam-User: X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 7DB7A4000E Authentication-Results: imf11.hostedemail.com; dkim=none; spf=pass (imf11.hostedemail.com: domain of regressions@leemhuis.info designates 80.237.130.52 as permitted sender) smtp.mailfrom=regressions@leemhuis.info; dmarc=none X-Stat-Signature: 63pycwp8mph586546f4mwbqtzya7rt5u X-HE-Tag: 1669712383-378450 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000184, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: [Note: this mail is primarily send for documentation purposes and/or for regzbot, my Linux kernel regression tracking bot. That's why I removed most or all folks from the list of recipients, but left any that looked like a mailing lists. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter out.] [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 20.10.22 06:23, Nathan Chancellor wrote: > [...] > For what it's worth, I just bisected a massive and visible performance > regression on my Threadripper 3990X workstation to commit f35b5d7d676e > ("mm: align larger anonymous mappings on THP boundaries"), which seems > directly related to this report/analysis. I initially noticed this > because my full set of kernel builds against mainline went from 2 hours > and 20 minutes or so to over 3 hours. Zeroing in on x86_64 allmodconfig, > which I used for the bisect: 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 f35b5d7d676e59e4 #regzbot title performance: mm: building Linux with clang takes a lot longer (~27 %) #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 replies to), as explained for in the Linux kernel's documentation; above webpage 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.