Received: by 10.192.165.156 with SMTP id m28csp322037imm; Tue, 17 Apr 2018 10:41:16 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+AQvdvBSXqM/obAgR8dNC9jp1ql/+04JKF0KFfJfSTH1VLyemHNGr7Iq35fkrHOJkrAX82 X-Received: by 10.98.62.87 with SMTP id l84mr2771092pfa.135.1523986876854; Tue, 17 Apr 2018 10:41:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523986876; cv=none; d=google.com; s=arc-20160816; b=vyruvzpnvK//YS+RbevV5y2q8X+FcK9uX0N7zlngShbt2tD+hq7w3xSDOwTQgVaEUG WzUIwq9KZp3If8ekhu7WQ70oPkAlc7X8saNSrzh+Xp9AYBirj+uuCTj+qZ6+qMkw4FED hN9/KJ/vrbiYtHYDJ+b5WflQ82OyOqIBDAZKd5SeRs2NJhtG1ZmQKu8ptxmxcyVOL/rR Q6a9E67jslyoGXLOB1wYsK8ZdLKkol8hkBBfVWSURBCBJbLHEozGaNXff0hLW0ZnlzyE V0JWT5k1L/3inxX9/vpyfZUR0u3vjZ0NIUQDZakR9quVV9c+ceMZuks43Dvc32ANmP4+ bZpA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=P2EQyuzIXnqTssSruv7trWZIZ4RZrFC7NsLcj9oQzv0=; b=p2We1SoiXUI98wcZfURc6Y4Xv5A2wSnsiFPSY931FnbGAjC9LPNBEaTyWmt4xDuA0v EdG0urKkbpD8lGOLKjhrnjYEwUZmWU/0PjXe/gP2GDBUTHpvUo/6hdSctJG0UYAePcPe VTz/XQEBwuKx9yZWyS7/iThYZKomVT9qHT7/pqvvYVyyiALUOfxpeeGxBk95UQG56pt8 jrzFYGS1dxkXSzw8N/raQBXsL8o7XUTgSqyV+fjvjcaDCmO1SJKJtlGiyp/V6XDhx55/ kchfoQ6l32adb0aJBHBaCn4hLcft6czf30nXe7cPBieqVau/v9SHqN6TavnwdYgv8ypu 6W9w== 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 r20si13802375pff.361.2018.04.17.10.41.02; Tue, 17 Apr 2018 10:41:16 -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 S1752725AbeDQRja (ORCPT + 99 others); Tue, 17 Apr 2018 13:39:30 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:46362 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751230AbeDQRj2 (ORCPT ); Tue, 17 Apr 2018 13:39:28 -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 502811435; Tue, 17 Apr 2018 10:39:28 -0700 (PDT) Received: from [192.168.11.82] (usa-sjc-mx-foss1.foss.arm.com [217.140.101.70]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9F50F3F587; Tue, 17 Apr 2018 10:39:23 -0700 (PDT) Subject: Re: [RFC PATCH v2 3/6] sched: Add over-utilization/tipping point indicator To: Leo Yan Cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Quentin Perret , Thara Gopinath , linux-pm@vger.kernel.org, Morten Rasmussen , Chris Redpath , Patrick Bellasi , Valentin Schneider , "Rafael J . Wysocki" , Greg Kroah-Hartman , Vincent Guittot , Viresh Kumar , Todd Kjos , Joel Fernandes , Juri Lelli , Steve Muckle , Eduardo Valentin References: <20180406153607.17815-1-dietmar.eggemann@arm.com> <20180406153607.17815-4-dietmar.eggemann@arm.com> <20180417142440.GB18509@leoy-ThinkPad-X240s> From: Dietmar Eggemann Message-ID: <03a64b8b-9d13-5480-8882-75ecac3d6042@arm.com> Date: Tue, 17 Apr 2018 19:39:21 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180417142440.GB18509@leoy-ThinkPad-X240s> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/17/2018 04:25 PM, Leo Yan wrote: >> @@ -5394,8 +5416,10 @@ enqueue_task_fair(struct rq *rq, struct task_struct *p, int flags) >> update_cfs_group(se); >> } >> >> - if (!se) >> + if (!se) { >> add_nr_running(rq, 1); >> + update_overutilized_status(rq); >> + } > > Maybe this isn't a good question, why only update overutilized flag > for enqueue flow but not for dequeue flow? [...] >> @@ -9955,6 +10009,8 @@ static void task_tick_fair(struct rq *rq, struct task_struct *curr, int queued) >> >> if (static_branch_unlikely(&sched_numa_balancing)) >> task_tick_numa(rq, curr); >> + >> + update_overutilized_status(rq); > > Can sched tick clear overutilized flag if under tipping point? No, only the load balancer for this particular sched domain level is able to clear the flag. We want to use the existing iteration over all cpus of the sched domain span to reset the flag.