Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2619707imm; Mon, 10 Sep 2018 04:07:15 -0700 (PDT) X-Google-Smtp-Source: ANB0Vdb0GAE3QV4CWicRRCqU90LMH6Y6vgdzr9yGnCWWD3HaQcAnuQ7YMxHlJmK7TCnXx/c2EfEj X-Received: by 2002:a63:495f:: with SMTP id y31-v6mr21740987pgk.32.1536577635192; Mon, 10 Sep 2018 04:07:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536577635; cv=none; d=google.com; s=arc-20160816; b=N/8O2mtKYN+hCNTNkWpiAN+9SbawR1Y3Sen1j63ak4V8w+Lk12v6l/U7lxqk9w6ce6 SNva+fjrsJ5T3VklF+n9TazCd237BnFaWAZCsJxC1L+bQEKk7eaJAC4uuzk6BKFPLzND RDmEWbwIGd9EvLYOHc2IIGp1UKjCinBKRiW797MjPYKFjEocJ8Dl9a5N9ds/ljgIiywk aM6Aau2OXoCbR8QwVr0mD92+BfatnwtbgQimVh9DIv5ZOA/M6xtZP6gSYdNb7t0Bp5ZW m5IlIGCD3m9bbXPgpicbbCm+YLYdJmAnPT2XqTd29rdcEI6M1YyvgKzNVnLTGia03aBa ikLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=wSToXNM4VewQ/WoBYT+3ed7GBLCexAmyQryMO5M8+x4=; b=iT2BFN9NnTX3jEM19CXc3mVCjMz+CjHlG4bKJV9bACLDqJa/+TBk7Gr9qYGNcntvGm 15j8e4iyQ8qQuzL+YuhPjFV6itVV3+aj3qLLULHmMK31xUmILRd6xa8icgni8QEt4h9m TbGmE4qbtQKQlPVAJjUeo5M6fYFkdLNxK9SmWmPWUF27+lfBWz1IiGCEQ1Pb0ORu+Cw9 3cipaZgGMtq1iVEHdgr3F7NUFbUAv7aOT+hhhYh3K4v1nTLLRo+lcrkB4xkdYMsilChe zYb3o2ydz8Rgg4FctT/CsxHtq5tabUXnRG1jkooe5BhYqMOUEIrd7OM74DCapZnZmEqJ myTA== ARC-Authentication-Results: i=1; mx.google.com; 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 m33-v6si17596004pgb.450.2018.09.10.04.06.59; Mon, 10 Sep 2018 04:07:15 -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; 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 S1727871AbeIJP70 (ORCPT + 99 others); Mon, 10 Sep 2018 11:59:26 -0400 Received: from foss.arm.com ([217.140.101.70]:55404 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727649AbeIJP70 (ORCPT ); Mon, 10 Sep 2018 11:59:26 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 695A218A; Mon, 10 Sep 2018 04:05:55 -0700 (PDT) Received: from [10.4.12.120] (e107158-lin.emea.arm.com [10.4.12.120]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7090C3F575; Mon, 10 Sep 2018 04:05:54 -0700 (PDT) Subject: Re: [RFC PATCH 3/4] sched/topology: remove smt_gain To: Srikar Dronamraju , Vincent Guittot Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org References: <1535548752-4434-1-git-send-email-vincent.guittot@linaro.org> <1535548752-4434-4-git-send-email-vincent.guittot@linaro.org> <20180904082424.GA2090@linux.vnet.ibm.com> <20180904093626.GA23936@linaro.org> <20180904103742.GC61288@linux.vnet.ibm.com> From: Qais Yousef Message-ID: <1370aa29-2b86-a199-05b9-a1995d65f966@arm.com> Date: Mon, 10 Sep 2018 12:05:52 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180904103742.GC61288@linux.vnet.ibm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/09/18 11:37, Srikar Dronamraju wrote: > * Vincent Guittot [2018-09-04 11:36:26]: > >> Hi Srikar, >> >> Le Tuesday 04 Sep 2018 à 01:24:24 (-0700), Srikar Dronamraju a écrit : >>> However after this change, capacity_orig of each SMT thread would be >>> 1024. For example SMT 8 core capacity_orig would now be 8192. >>> >>> smt_gain was suppose to make a multi threaded core was slightly more >>> powerful than a single threaded core. I suspect if that sometimes hurt >> Is there system with both single threaded and multi threaded core ? >> That was the main open point for me (and for Qais too) >> > I dont know of any systems that have come with single threaded and > multithreaded. However some user can still offline few threads in a core > while leaving other cores untouched. I dont really know why somebody > would want to do it. For example, some customer was toying with SMT 3 > mode in a SMT 8 power8 box. What was the customer trying to achieve by this? Did this end up being useful? If we get mixed SMT 3 and SMT 8 in the system we might have issues, but again I don't see how this makes sense from system point of view. I don't think power savings will be significant by turning off few hardware threads since the core which I'd expect to be the main energy consumer is still on. From performance perspective, SMT 3 might have less contention (hence better 'performance'), but we don't do anything special to decide to schedule work in this case to take advantage of that. So I don't think the setup is useful to cater for or encourage. -- Qais Yousef