Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp772142yba; Wed, 15 May 2019 09:39:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqwwPf+cTpZHY13/Vy42DEuyR1hpYQLHo6LcTIcQ09hqudTfcCbyM8HQB4uBMwbZu9IONk1K X-Received: by 2002:aa7:8c48:: with SMTP id e8mr48405606pfd.80.1557938379039; Wed, 15 May 2019 09:39:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557938379; cv=none; d=google.com; s=arc-20160816; b=RNwZk9d5s6owLYDOk+U/Kj4TTOrHF1QfexjwksXdYrcFD7GneUQCV7CEOnuNjrq13I Kotv7YiV8glZ6zjhwlL5J3rwAG5wnllYha+YIuki3sh7iCSRKW3dSJ/iHJoENGT1O+FR JuaDlruAQJvFdHeY3/3hxKghhbZSaJHsFPsJ252uKG4UnN+TTBHFkBg2WHRc74eM9YjN Roj16pfjOtKhYb+goj7ervkVgpCfVBWx16TKp9OyqxA0bT6hrp1dNz7M8WtfFy9jcORn fTKMGY2VdzhcUtKYFI+anmhpLupi9WSagWVVaJHTP+j8+RmcKUH6LzvS4eVbfF48p+Th tR9A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=OtMvEXRStSFfAAGIbWQmGKZWz5rWXJEj2aQ6RYI6efI=; b=wTs8F12iR7coDwIMLZgwb0Xq4mGORyJ8PtuCpkLh3y2sXOnRjlVCgpah0IBmR6elxE ZfVFX40lwY/9DtmCbC+Q+dG4VrLMHsXbIJnS2ShVMf4kjalopjS1wjR7iRJSIMqTMPmq 6E62IvS5iBOz5bNpU3mkrNQQztpqxrT7vAgsqVsZ+RrOZylqnXvR5H/TDxuwk31MugrZ Ook7xG6M5/qGSHzvm+WAdK3F2GrYtVGmBDhcFTe7MDrve0nrLQQz6yqUqLio5+DCBnOb C0As38S+TF+mm0IZDCVvN1rLym0JiyyiEzexunGVBT+RrKGwF0QLhXOVaWQprgcrDBm9 y5nA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b="bIpHC5/O"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i64si2199890pgc.78.2019.05.15.09.39.23; Wed, 15 May 2019 09:39:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b="bIpHC5/O"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726888AbfEOQh6 (ORCPT + 99 others); Wed, 15 May 2019 12:37:58 -0400 Received: from merlin.infradead.org ([205.233.59.134]:48744 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726520AbfEOQh6 (ORCPT ); Wed, 15 May 2019 12:37:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=OtMvEXRStSFfAAGIbWQmGKZWz5rWXJEj2aQ6RYI6efI=; b=bIpHC5/OJWt+EW0yH5oJoix53 Yo6l9W5Z/jkqvOKRRVXc4gbZFnZ4MnECgs5PXJ/ieEumhruTuadQshGB6iGJtG8UuTLkOgVR/VJE9 a5BiM2mmPAC+SuQoK8A6ct7iakYS/2l9HOSE1aOxYv6p2JZ1EsRrJKEH9mQssVVZVGWTmnjgw6hps usaBuZE6qgazdHL6SAMJ9xznNW0gYBl2AwCrXUACQAlDiMrvvgfVdkWJ8Pi/9kxl3/gLtbn1LXBpN /i7OYeja6dF5WPZ7NiMGBozw9RDvzMz1joQqMcRpVD4DJVPLNIJRvDPbUTRiHJI0tGPL4xURxe+dK VYEmHiZkA==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1hQwuf-0001Fy-Dt; Wed, 15 May 2019 16:37:53 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 0D2042029906B; Wed, 15 May 2019 18:37:52 +0200 (CEST) Date: Wed, 15 May 2019 18:37:52 +0200 From: Peter Zijlstra To: Parth Shah Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, mingo@redhat.com, dietmar.eggemann@arm.com, dsmythies@telus.net Subject: Re: [RFCv2 4/6] sched/fair: Define core capacity to limit task packing Message-ID: <20190515163751.GW2589@hirez.programming.kicks-ass.net> References: <20190515135322.19393-1-parth@linux.ibm.com> <20190515135322.19393-5-parth@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190515135322.19393-5-parth@linux.ibm.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 15, 2019 at 07:23:20PM +0530, Parth Shah wrote: > The task packing on a core needs to be bounded based on its capacity. This > patch defines a new method which acts as a tipping point for task packing. > > The Core capacity is the method which limits task packing above certain > point. In general, the capacity of a core is defined to be the aggregated > sum of all the CPUs in the Core. > > Some architectures does not have core capacity linearly increasing with the > number of threads( or CPUs) in the core. For such cases, architecture > specific calculations needs to be done to find core capacity. > > The `arch_scale_core_capacity` is currently tuned for `powerpc` arch by > scaling capacity w.r.t to the number of online SMT in the core. > > The patch provides default handler for other architecture by scaling core > capacity w.r.t. to the capacity of all the threads in the core. > > ToDo: SMT mode is calculated each time a jitter task wakes up leading to > redundant decision time which can be eliminated by keeping track of online > CPUs during hotplug task. Urgh, we just got rid of capacity for SMT. Also I don't think the above clearly defines your metric.