Received: by 10.223.185.116 with SMTP id b49csp615276wrg; Tue, 20 Feb 2018 05:07:27 -0800 (PST) X-Google-Smtp-Source: AH8x226bBdEVau2NdvbzUPsPMaldfRqU7zqDfMsFjU8SLp5e3IGJhmxepYafywMa8tQrIjkxqAp9 X-Received: by 10.98.160.90 with SMTP id r87mr16551649pfe.151.1519132047077; Tue, 20 Feb 2018 05:07:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519132047; cv=none; d=google.com; s=arc-20160816; b=wdrALji9V0Go3/kn0QTN6n5qZcltCt355d4bqV1hjiAh7UnUxSsvpg6mhxGCNXBorx /VGjQM8EZ3qywb7pY7gerDA+gmjDf0LpnNVl06MRGDcqEBq7mvUZ8HkTwL3FbGp0+/AL FasRJga6/0cBsXcNsK2xsZchsOslbHU07UF7F4aM3aMz2laSfIvfrBfe1xeqCRspGUoe RUB8c27YTGpv2t2hmX1MNDfAjIcbk+E+BSRglJK/kVurlfDGWN5mEzWZtI4bhIVopbkM /A+Pd9KiZbQpDEFRuJ5FQCRBe/sTQhuFnAtgiah0Og3ThlBr8yf/GUnqW938EWY+K5Wo zh6g== 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:arc-authentication-results; bh=ljP7+OczTdYIzR6IcwPRx+nSzaWK35PSG8b6aKslNbo=; b=Bsz0P8cpRLb0pXtYxB4h2JCQCRQYTkKg1TMYs89rXtk56TCFrorebvemJCBwuUQGGX JlZXQNMy36bwYIOzrbC0+HUsEK8MGEwrfhQuPba/OQOWkwEuvQOcbZAfRBmU/uAYHJz3 VOmkMoyCvgELQM8cxMXy370I0h85+expctmcSYK56Ih9ujlha/3aE1Z5wSqJ4zdi+QBk tx5X19NXJ0kz4Uz6eCG6Dmm6EDgKQEfSbXi3A0CYTrBm7aX8Z0yXqG5Knmi3lzA06XN+ Sa4LcpHisSLHTGMaw7wcnIRIp1cdVGhtXVjv4JLNc0UU1IjJ5Lkwf2rdRbwWH2vsY9KV orOA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=oGopfyhi; 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 q79si7667542pfi.105.2018.02.20.05.06.52; Tue, 20 Feb 2018 05:07:27 -0800 (PST) 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=oGopfyhi; 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 S1752189AbeBTNFU (ORCPT + 99 others); Tue, 20 Feb 2018 08:05:20 -0500 Received: from merlin.infradead.org ([205.233.59.134]:55426 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751936AbeBTNCB (ORCPT ); Tue, 20 Feb 2018 08:02:01 -0500 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=ljP7+OczTdYIzR6IcwPRx+nSzaWK35PSG8b6aKslNbo=; b=oGopfyhimFjVGim9UUBvyvf9G wxdscelAMgKz+ZHc88x2Ob8L1VqtCnlGCwEjGNUVDjuVLBrzs09xChQ4jP5Qinup3X9Jr71LyT0CJ EIiCbdfNtnh2vnsDgCk0jyNszKB3rmAIR1XjbhQ9mkUJRPQp47cLQU9Nohj91+mFHWkQVif4R34df g3cgFaZCDN6PuW3JtWlJvZRsKg3ZmGz/W49VbweGmqzcMgCbwR28wCAeOP0foPJrKtIaM9v3wg7Mx B5yBMAhurcg7NsplI4bMI18QAj8QO+bhjPcyL3PwQn7wc+0VsbLFcAxqd0vb9tiY9jNI8HL7AfGR3 LJ4743LdA==; 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.89 #1 (Red Hat Linux)) id 1eo7YS-00084G-HK; Tue, 20 Feb 2018 13:01:56 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id D5B412038D444; Tue, 20 Feb 2018 14:01:53 +0100 (CET) Date: Mon, 19 Feb 2018 15:53:35 +0100 From: Peter Zijlstra To: Morten Rasmussen Cc: mingo@redhat.com, valentin.schneider@arm.com, dietmar.eggemann@arm.com, vincent.guittot@linaro.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 4/7] sched/fair: Avoid unnecessary balancing of asymmetric capacity groups Message-ID: <20180219145335.GN25235@hirez.programming.kicks-ass.net> References: <1518711654-23503-1-git-send-email-morten.rasmussen@arm.com> <1518711654-23503-5-git-send-email-morten.rasmussen@arm.com> <20180219145012.GH25181@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180219145012.GH25181@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 19, 2018 at 03:50:12PM +0100, Peter Zijlstra wrote: > On Thu, Feb 15, 2018 at 04:20:51PM +0000, Morten Rasmussen wrote: > > On systems with asymmetric cpu capacities, a skewed load distribution > > might yield better throughput than balancing load per group capacity. > > For example, preferring high capacity cpus for compute intensive tasks > > leaving low capacity cpus idle rather than balancing the number of idle > > cpus across different cpu types. Instead, let load-balance back off if > > the busiest group isn't really overloaded. > > I'm sorry. I just can't seem to make sense of that today. What? Aah, you're saying that is we have 4+4 bit.little and 4 runnable tasks, we would like them running on our big cluster and leave the small cluster entirely idle, instead of runnint 2+2. So what about this DynamicQ nonsense? Or is that so unstructured we can't really do anything sensible with it?