Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp916044pxb; Fri, 22 Jan 2021 02:27:56 -0800 (PST) X-Google-Smtp-Source: ABdhPJzeUG0uepcgihg5WPpEAA/uI4/mJXbkNmwjRfST4zF7e0xkuKp2ahPyKq23mes8gXpNX29K X-Received: by 2002:a50:d685:: with SMTP id r5mr2737814edi.248.1611311276099; Fri, 22 Jan 2021 02:27:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611311276; cv=none; d=google.com; s=arc-20160816; b=uvqF1aLk/lZzAqyo73c5G54IhnD3g5DjHKSMWrd813bvarXkSMCKymHoii1UXDa4BT +mINx0Vf/JHbjNAMBnm0TBPyv/FBw2Q9M3aNimGrrNw+M3QxfkiAuxEbMdc6h4dywlzA F9OG7FzFXJI95Bx5971kTyBuhN6eCPTGOuNtdzEauyrQBjkiHqeaFTQlaG3pR1HM298r hMx+0s/CxdniHCMIF15G7PnZjdvAOE3FbUOdn3rORok6XdAu1L+yynDOEX784iAWPKmB KATrYOLji1ez8pBFWFlWKkSUkFeaASXHQY/hT7eAWY/MJVq8lObP5xWfM/pFPTDus2UR 9mjg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=EAQasttylw+/rr1P7ikL0DgTc3UftjM7Y84q+Ga32Fc=; b=yK3v7w7wtqF4nUpTd9TxwxM+H9w3Q61S0nz9OyQYz+CZ/uAKTjv/SZMXEHBjBtkyjb NenZDSBm7xGI017OzMgB/Ji0yqeEceOtDpe1YACLyZR6K6j1OZCWEF64bZ0gif6SKvw5 Vklvel9f0upqMcm2BcDTdUB8ic8jtVRbJGYX7qgNRMoPdyYU5jwl4l8e/eRa6rtXl4o7 jSTKNhcX8OzBSu5zdGJySRxDQ6kWj6WYyw1+8/THYLZ69qR2IqKio2GpH6MTHT1+6EVa azc5baVr7y6EBv7tz4JJnlDBnqM9ZZWaNOC75ZT32D87sf0M0r40uJ+D8U5Fmpn8Ny/e kp8Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s25si2786627ejz.751.2021.01.22.02.27.32; Fri, 22 Jan 2021 02:27:56 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727134AbhAVKZ3 (ORCPT + 99 others); Fri, 22 Jan 2021 05:25:29 -0500 Received: from outbound-smtp17.blacknight.com ([46.22.139.234]:36813 "EHLO outbound-smtp17.blacknight.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727847AbhAVKPt (ORCPT ); Fri, 22 Jan 2021 05:15:49 -0500 Received: from mail.blacknight.com (pemlinmail06.blacknight.ie [81.17.255.152]) by outbound-smtp17.blacknight.com (Postfix) with ESMTPS id 6CC7E1C75DF for ; Fri, 22 Jan 2021 10:14:53 +0000 (GMT) Received: (qmail 13926 invoked from network); 22 Jan 2021 10:14:53 -0000 Received: from unknown (HELO techsingularity.net) (mgorman@techsingularity.net@[84.203.22.4]) by 81.17.254.9 with ESMTPSA (AES256-SHA encrypted, authenticated); 22 Jan 2021 10:14:53 -0000 Date: Fri, 22 Jan 2021 10:14:51 +0000 From: Mel Gorman To: Vincent Guittot Cc: Peter Zijlstra , Ingo Molnar , Li Aubrey , Qais Yousef , LKML Subject: Re: [PATCH v3 0/5] Scan for an idle sibling in a single pass Message-ID: <20210122101451.GV3592@techsingularity.net> References: <20210119112211.3196-1-mgorman@techsingularity.net> <20210119120220.GS3592@techsingularity.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 22, 2021 at 10:30:52AM +0100, Vincent Guittot wrote: > Hi Mel, > > On Tue, 19 Jan 2021 at 13:02, Mel Gorman wrote: > > > > On Tue, Jan 19, 2021 at 12:33:04PM +0100, Vincent Guittot wrote: > > > On Tue, 19 Jan 2021 at 12:22, Mel Gorman wrote: > > > > > > > > Changelog since v2 > > > > o Remove unnecessary parameters > > > > o Update nr during scan only when scanning for cpus > > > > > > Hi Mel, > > > > > > I haven't looked at your previous version mainly because I'm chasing a > > > performance regression on v5.11-rcx which prevents me from testing the > > > impact of your patchset on my !SMT2 system. > > > Will do this as soon as this problem is fixed > > > > > > > Thanks, that would be appreciated as I do not have access to a !SMT2 > > system to do my own evaluation. > > I have been able to run tests with your patchset on both large arm64 > SMT4 system and small arm64 !SMT system and patch 3 is still a source > of regression on both. Decreasing min number of loops to 2 instead of > 4 and scaling it with smt weight doesn't seem to be a good option as > regressions disappear when I remove them as I tested with the patch > below > > hackbench -l 2560 -g 1 on 8 cores arm64 > v5.11-rc4 : 1.355 (+/- 7.96) > + sis improvement : 1.923 (+/- 25%) > + the patch below : 1.332 (+/- 4.95) > > hackbench -l 2560 -g 256 on 8 cores arm64 > v5.11-rc4 : 2.116 (+/- 4.62%) > + sis improvement : 2.216 (+/- 3.84%) > + the patch below : 2.113 (+/- 3.01%) > > So starting with a min of 2 loops instead of 4 currently and scaling > nr loop with smt weight doesn't seem to be a good option and we should > remove it for now > Ok Note that this is essentially reverting the patch. As you remove "nr *= sched_smt_weight", the scan is no longer proportional to cores, it's proportial to logical CPUs and the rest of the patch and changelog becomes meaningless. On that basis, I'll queue tests over the weekend that remove this patch entirely and keep the CPU scan as a single pass. -- Mel Gorman SUSE Labs