Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp413706ybi; Fri, 21 Jun 2019 01:45:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqw+vkmb7RPhcr5FkLpZkHnG7PH99skVKmQRY+ovsbzOmM838Ot9/h2NpHXAv+6NfcL+Oc8j X-Received: by 2002:a65:6102:: with SMTP id z2mr16677859pgu.194.1561106700432; Fri, 21 Jun 2019 01:45:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561106700; cv=none; d=google.com; s=arc-20160816; b=xxWYN2Oojdg25Az/ksC3r0qiZkhgcxRz8OHQsTXvTcN3h0hxoTnvNlwRRxrwBn5+jM sOZ7ZNxOE1Q42YyiwxI/B/gN0Q5RdpnAlp0VoXHZOCzw88vuM8W6VcWAPY2evddcWpFe WjcZSMmFvaI8EOVf42fhpGXaguU2R6m6I3GmeQ+UrEB9kJmh60hVlbLPMndo2TuKjp7V eFQpeixEAvjGj3unluOJYK0eMkvBVb+8JJJb0gBEb1Veqy7JUgjMxLGNRsemOa7Y2ADm Vpu6kpgFhXt4C6ZP6Pz05ELJoC50M6upVTKi1Z6WqUjvTekjNC7qk/UBAPaYHNGAQHx4 CDdg== 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:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=pS5Zqiov5XNQ1G/N0uzkZrrK9Oc4KNYPokNP4NoQHMk=; b=0DND2L9ePDWqpWRGpbHsD4wjFr84NQ21+Lx1p6cNnjYYJPY3F9LoBV/eQgCKjyJHxg cX7fuS1fuMFVEQua6BDQra8OgazwvFmiiRWlDk8GqwI+JNr6j8uYWntuo2o1YCcOdrHQ 3IL2D+CnPCjyMEpIChDzagXzHkVqZrJgKeR0SZ5ZdClKOKR94suSoTx5ZNbsjhrDmM4l Si5sk3+YM+ibK51AMERDb40L9oE5eI0XkXEJTfUMUGXUDNabK2aQRZhh079ccLbrwkbB 5TG03w/vnMOamCAOgY9AWWQKANnpd025tZzQ17tLQYCxkEe4CsGxZksTJUsUT4VUEvKB FkPg== 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 t11si1980394pgp.153.2019.06.21.01.44.45; Fri, 21 Jun 2019 01:45:00 -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 S1726813AbfFUInW (ORCPT + 99 others); Fri, 21 Jun 2019 04:43:22 -0400 Received: from foss.arm.com ([217.140.110.172]:51108 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726740AbfFUInO (ORCPT ); Fri, 21 Jun 2019 04:43:14 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 8493D1595; Fri, 21 Jun 2019 01:43:13 -0700 (PDT) Received: from e110439-lin.cambridge.arm.com (e110439-lin.cambridge.arm.com [10.1.194.43]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 31D673F246; Fri, 21 Jun 2019 01:43:11 -0700 (PDT) From: Patrick Bellasi To: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org Cc: Ingo Molnar , Peter Zijlstra , Tejun Heo , "Rafael J . Wysocki" , Vincent Guittot , Viresh Kumar , Paul Turner , Quentin Perret , Dietmar Eggemann , Morten Rasmussen , Juri Lelli , Todd Kjos , Joel Fernandes , Steve Muckle , Suren Baghdasaryan , Alessio Balsini Subject: [PATCH v10 15/16] sched/core: uclamp: Use TG's clamps to restrict TASK's clamps Date: Fri, 21 Jun 2019 09:42:16 +0100 Message-Id: <20190621084217.8167-16-patrick.bellasi@arm.com> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190621084217.8167-1-patrick.bellasi@arm.com> References: <20190621084217.8167-1-patrick.bellasi@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When a task specific clamp value is configured via sched_setattr(2), this value is accounted in the corresponding clamp bucket every time the task is {en,de}qeued. However, when cgroups are also in use, the task specific clamp values could be restricted by the task_group (TG) clamp values. Update uclamp_cpu_inc() to aggregate task and TG clamp values. Every time a task is enqueued, it's accounted in the clamp_bucket defining the smaller clamp between the task specific value and its TG effective value. This allows to: 1. ensure cgroup clamps are always used to restrict task specific requests, i.e. boosted only up to the effective granted value or clamped at least to a certain value 2. implement a "nice-like" policy, where tasks are still allowed to request less then what enforced by their current TG This mimics what already happens for a task's CPU affinity mask when the task is also in a cpuset, i.e. cgroup attributes are always used to restrict per-task attributes. Do this by exploiting the concept of "effective" clamp, which is already used by a TG to track parent enforced restrictions. Apply task group clamp restrictions only to tasks belonging to a child group. While, for tasks in the root group or in an autogroup, only system defaults are enforced. Signed-off-by: Patrick Bellasi Cc: Ingo Molnar Cc: Peter Zijlstra Cc: Tejun Heo --- kernel/sched/core.c | 28 +++++++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index f09712f65017..8070e11cafa0 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -862,16 +862,42 @@ unsigned int uclamp_rq_max_value(struct rq *rq, unsigned int clamp_id, return uclamp_idle_value(rq, clamp_id, clamp_value); } +static inline struct uclamp_se +uclamp_tg_restrict(struct task_struct *p, unsigned int clamp_id) +{ + struct uclamp_se uc_req = p->uclamp_req[clamp_id]; +#ifdef CONFIG_UCLAMP_TASK_GROUP + struct uclamp_se uc_max; + + /* + * Tasks in autogroups or root task group will be + * restricted by system defaults. + */ + if (task_group_is_autogroup(task_group(p))) + return uc_req; + if (task_group(p) == &root_task_group) + return uc_req; + + uc_max = task_group(p)->uclamp[clamp_id]; + if (uc_req.value > uc_max.value || !uc_req.user_defined) + return uc_max; +#endif + + return uc_req; +} + /* * The effective clamp bucket index of a task depends on, by increasing * priority: * - the task specific clamp value, when explicitly requested from userspace + * - the task group effective clamp value, for tasks not either in the root + * group or in an autogroup * - the system default clamp value, defined by the sysadmin */ static inline struct uclamp_se uclamp_eff_get(struct task_struct *p, unsigned int clamp_id) { - struct uclamp_se uc_req = p->uclamp_req[clamp_id]; + struct uclamp_se uc_req = uclamp_tg_restrict(p, clamp_id); struct uclamp_se uc_max = uclamp_default[clamp_id]; /* System default restrictions always apply */ -- 2.21.0