From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754942AbdKJHZU (ORCPT ); Fri, 10 Nov 2017 02:25:20 -0500 Received: from mail-wr0-f170.google.com ([209.85.128.170]:52761 "EHLO mail-wr0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750800AbdKJHZS (ORCPT ); Fri, 10 Nov 2017 02:25:18 -0500 X-Google-Smtp-Source: ABhQp+TkTQi8gV2JHFwh6Xm1ceR0ZVDeqKiCi/8Y2+2I+nqsKMwJ+XacB26WukRVkqMveUadz4C+iw== Date: Fri, 10 Nov 2017 08:25:13 +0100 From: Ingo Molnar To: "Rafael J. Wysocki" Cc: WANG Chao , Linus Torvalds , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Vikas Shivappa , Kate Stewart , Len Brown , Greg Kroah-Hartman , Philippe Ombredanne , Mathias Krause , x86@kernel.org, "Rafael J. Wysocki" , Linux PM Subject: Re: [PATCH] x86: use cpufreq_quick_get() for /proc/cpuinfo "cpu MHz" again Message-ID: <20171110072513.mp5p7o7pledumoyi@gmail.com> References: <20171109103814.70688-1-chao.wang@ucloud.cn> <6583ed1f-3ea3-c7fd-7e69-1430c8387e54@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6583ed1f-3ea3-c7fd-7e69-1430c8387e54@intel.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Rafael J. Wysocki wrote: > Hi Linus, > > On 11/9/2017 11:38 AM, WANG Chao wrote: > > Commit 941f5f0f6ef5 (x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo) caused > > a serious performance issue when reading from /proc/cpuinfo on system > > with aperfmperf. > > > > For each cpu, arch_freq_get_on_cpu() sleeps 20ms to get its frequency. > > On a system with 64 cpus, it takes 1.5s to finish running `cat > > /proc/cpuinfo`, while it previously was done in 15ms. > > Honestly, I'm not sure what to do to address this ATM. > > The last requested frequency is only available in the non-HWP case, so it > cannot be used universally. This is a serious regression that needs to be fixed ASAP, because the slowdown is utterly ridiculous on a 120 CPU system: fomalhaut:~> time cat /proc/cpuinfo >/dev/null real 0m2.689s user 0m0.001s sys 0m0.007s Thanks, Ingo