Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp5365956pxu; Wed, 21 Oct 2020 23:33:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy9fEtNM40faIBGNugLWu2iKbWQhYGrt1UVaJ0IDgU3X8wBcnU8L9LpN7Nnv/MlpcTQ0i1I X-Received: by 2002:a05:6402:c6:: with SMTP id i6mr872604edu.363.1603348433040; Wed, 21 Oct 2020 23:33:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603348433; cv=none; d=google.com; s=arc-20160816; b=d6qL42ANaJvXuupUb57tCSrz0AjIJZMhcYvQq+GyKmAidiFba1S5HyVxV03Hv7nvQT FPHT2/DCg0ddscjXfBELLrU1aab8ocL+J5gqXwHIhNOOTS3cRF5E5EYZM9feow5uLnZA u5jkGqJTHIvM6EJKbAcXiP0NbzrbImdE3uuKyxpOEY/T7cpCXtHtVVDw97xPzrfpkX2r E65DC8gUdrEmLoc43/YAOlvfAnzEn06tuxifJApxwvH4hxqqazUDJk9chNSHNmvMkLXC EAiV9IU/K1yJRGiPB/TT0Lc5swKfKzyZBQ6o1ZFjpkYGwpBh3udhkA87a+XN9LgMhErH /z/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=+6MIFaImrXefKdCqnZBSkZ2vkFeh3W+l33UsqX/WGXg=; b=YFJmwyB+GYBOWQBjAsswlE0BasgR6NgGqxUtHEEB5CdqM0KlZGktbvM4/MzNd1l5ia jARSSaQHHJyhUz8CNWKxZYcASWQXmRy7TlY/TOQlqnfSl2BBMy5Yui4kpr3Ds65ovDgI AIPkM6IaXcd5R24/o97nnJTk3TeQMkBA0YqC4DLydLpLpz3jRxR6dNbG5S0OqrmZI1eY r0MCGiuQDKAcbsbdz4RTxngdgBAbE8NW5OAyAyhAYleYQC84jBj29wYilD0syMVJIYKF mv8Os+CXgKT49Q6rdLcXCAtQMDJrVhNOY0GeT3Qv91rMqTp/FsTDarPU4dd1T+RQSu8c nuzQ== 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 v7si544902edd.62.2020.10.21.23.33.31; Wed, 21 Oct 2020 23:33:53 -0700 (PDT) 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 S2503953AbgJUSPv (ORCPT + 99 others); Wed, 21 Oct 2020 14:15:51 -0400 Received: from cloudserver094114.home.pl ([79.96.170.134]:48360 "EHLO cloudserver094114.home.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2409610AbgJUSPv (ORCPT ); Wed, 21 Oct 2020 14:15:51 -0400 Received: from 89-77-60-66.dynamic.chello.pl (89.77.60.66) (HELO kreacher.localnet) by serwer1319399.home.pl (79.96.170.134) with SMTP (IdeaSmtpServer 0.83.491) id c132fe0aa49c926b; Wed, 21 Oct 2020 20:15:48 +0200 From: "Rafael J. Wysocki" To: Julia Lawall Cc: Peter Zijlstra , Mel Gorman , Ingo Molnar , kernel-janitors@vger.kernel.org, Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Daniel Bristot de Oliveira , linux-kernel@vger.kernel.org, Valentin Schneider , Gilles Muller , viresh.kumar@linaro.org, srinivas.pandruvada@linux.intel.com Subject: Re: [PATCH] sched/fair: check for idle core Date: Wed, 21 Oct 2020 20:15:47 +0200 Message-ID: <20581608.8Dxr8OdOFj@kreacher> In-Reply-To: References: <1603211879-1064-1-git-send-email-Julia.Lawall@inria.fr> <20201021121950.GF2628@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, October 21, 2020 2:42:20 PM CEST Julia Lawall wrote: > > On Wed, 21 Oct 2020, Peter Zijlstra wrote: > > > On Wed, Oct 21, 2020 at 01:56:55PM +0200, Julia Lawall wrote: > > > Prior to 5.8, my machine was using intel_pstate and had few background > > > tasks. Thus the problem wasn't visible in practice. Starting with 5.8 > > > the kernel decided that intel_cpufreq would be more appropriate, which > > > introduced kworkers every 0.004 seconds on all cores. > > > > That still doesn't make any sense. Are you running the legacy on-demand > > thing or something? > > > > Rafael, Srinivas, Viresh, how come it defaults to that? > > The relevant commits are 33aa46f252c7, and 39a188b88332 that fixes a small > bug. I have a Intel(R) Xeon(R) CPU E7-8870 v4 @ 2.10GHz that does not > have the HWP feature, even though the cores seemed to be able to change > their frequencies at the hardware level. That's in the range of "turbo" P-states (if a P-state above a certain threshold is requested by the governor, the processor has a license to choose P-states in the range above this threshold by itself). Cheers!