Received: by 10.192.165.156 with SMTP id m28csp570454imm; Fri, 13 Apr 2018 04:16:35 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/13dacqoo42co0uWVcTwNX0Z4JKUSKKsnnpnslNbVwywSGdPxsjLOebXXxK3gWx4Zp3MLs X-Received: by 10.101.81.11 with SMTP id f11mr205412pgq.137.1523618195789; Fri, 13 Apr 2018 04:16:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523618195; cv=none; d=google.com; s=arc-20160816; b=bHsnqv0/JV/hSPuTPNv/YFCxA95KglWsBBf0wm75xVPR+w5k8ASfT4qaSBQuoo8/6O d2yYed3eZD6knDFzVyvQm9Qu754D+dsM6PUj+Tdv8GoZZsMQ+onOElS75o+MIEmJ1m0B wbcVZ7Sc5EM/J2ZhbNJonLTmCoL++hFNA1jhzLQhnZwy9T9VPl1tbUFfPKqnwNjYSg69 dCh6dewUctmtIqGMtQL651BiozbY6fUMqqu7KnHzgrn72tKd5WheiJKJAU/5wKx7cUaY N+w1tl4b4Gl3qos1G6/heyWvRQ6focLoCzepSOjgqRo0D/r+TwUg2+HH0wkRhi1HrQy5 +bbw== 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:arc-authentication-results; bh=iV24ijyJFo5kZatpPC9v0S2bsUUFeY9+iHgArDOK4jc=; b=TvQJChYPagUnxGyRpvX+LtaT3NRgyWZMZo7Cs+yBMebtjUxl/0qVTKPaN7OjjMV3Rs Q7loqJeSrvQrnjaSDvgyPH9zaaX27oq7Ctuj0QFejXn/UNOyqjd0GHvOkwqpAs67fZ0k TuP8dHUaEtni67NePFgTbEhuEPjLiTTjZw5MxZo6fczUgHA98rrKmHWF0D6/F6bT1sbY dOH6b4dO6w3Z3H0morNI2C04/9S/uM1x+xbnFgIkPeNsMRdMv/P/ojxSTKnV/mn9IWPx HBeu7Cg3Cg3iinwSxXbEnGAsq50Oj8Xz0qW50cmrlxtMaj3oCwffNBPVF6G2jVYE6qNO Rokw== 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 r18si4462814pfe.168.2018.04.13.04.16.21; Fri, 13 Apr 2018 04:16:35 -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 S1754283AbeDMLPS (ORCPT + 99 others); Fri, 13 Apr 2018 07:15:18 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:41418 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754045AbeDMLPQ (ORCPT ); Fri, 13 Apr 2018 07:15:16 -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 036131435; Fri, 13 Apr 2018 04:15:16 -0700 (PDT) Received: from e110439-lin (e110439-lin.cambridge.arm.com [10.1.210.68]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 767B83F592; Fri, 13 Apr 2018 04:15:13 -0700 (PDT) Date: Fri, 13 Apr 2018 12:15:10 +0100 From: Patrick Bellasi To: Peter Zijlstra Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, Ingo Molnar , Tejun Heo , "Rafael J . Wysocki" , Viresh Kumar , Vincent Guittot , Paul Turner , Dietmar Eggemann , Morten Rasmussen , Juri Lelli , Joel Fernandes , Steve Muckle Subject: Re: [PATCH 1/7] sched/core: uclamp: add CPU clamp groups accounting Message-ID: <20180413111510.GS14248@e110439-lin> References: <20180409165615.2326-1-patrick.bellasi@arm.com> <20180409165615.2326-2-patrick.bellasi@arm.com> <20180413084302.GR4043@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180413084302.GR4043@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13-Apr 10:43, Peter Zijlstra wrote: > On Mon, Apr 09, 2018 at 05:56:09PM +0100, Patrick Bellasi wrote: > > +static inline void uclamp_task_update(struct rq *rq, struct task_struct *p) > > +{ > > + int cpu = cpu_of(rq); > > + int clamp_id; > > + > > + /* The idle task does not affect CPU's clamps */ > > + if (unlikely(p->sched_class == &idle_sched_class)) > > + return; > > + /* DEADLINE tasks do not affect CPU's clamps */ > > + if (unlikely(p->sched_class == &dl_sched_class)) > > + return; > > + > > + for (clamp_id = 0; clamp_id < UCLAMP_CNT; ++clamp_id) { > > + if (uclamp_task_affects(p, clamp_id)) > > + uclamp_cpu_put(p, cpu, clamp_id); > > + else > > + uclamp_cpu_get(p, cpu, clamp_id); > > + } > > +} > > Is that uclamp_task_affects() thing there to fix up the fact you failed > to propagate the calling context (enqueue/dequeue) ? Not really, it's intended by design: we back annotate the clamp_group a task has been refcounted in. The uclamp_task_affects() tells if we are refcounted now and then we know from the back-annotation from which refcounter we need to remove the task. I found this solution much less racy and effective in avoiding to screw up the refcounter whenever we look at a task at either dequeue/migration time and these operations can overlaps with the slow-path. Meaning, when we change the task specific clamp_group either via syscall or cgroups attributes. IOW, the back annotation allows to decouple refcounting from clamp_group configuration in a lockless way. > I find this code _really_ hard to read... Hope the explanation above clarifies the logic... do you have alternative proposals? > > @@ -743,6 +929,7 @@ static inline void enqueue_task(struct rq *rq, struct task_struct *p, int flags) > > if (!(flags & ENQUEUE_RESTORE)) > > sched_info_queued(rq, p); > > > > + uclamp_task_update(rq, p); > > p->sched_class->enqueue_task(rq, p, flags); > > } > > > > @@ -754,6 +941,7 @@ static inline void dequeue_task(struct rq *rq, struct task_struct *p, int flags) > > if (!(flags & DEQUEUE_SAVE)) > > sched_info_dequeued(rq, p); > > > > + uclamp_task_update(rq, p); > > p->sched_class->dequeue_task(rq, p, flags); > > } > > -- #include Patrick Bellasi