Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754917AbcKJKEJ (ORCPT ); Thu, 10 Nov 2016 05:04:09 -0500 Received: from foss.arm.com ([217.140.101.70]:44964 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752760AbcKJKEI (ORCPT ); Thu, 10 Nov 2016 05:04:08 -0500 Date: Thu, 10 Nov 2016 10:04:28 +0000 From: Juri Lelli To: luca abeni Cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Ingo Molnar , Claudio Scordino , Steven Rostedt Subject: Re: [RFC v3 2/6] Improve the tracking of active utilisation Message-ID: <20161110100428.GH16920@e106622-lin> References: <1477317998-7487-1-git-send-email-luca.abeni@unitn.it> <1477317998-7487-3-git-send-email-luca.abeni@unitn.it> <20161101164604.GB2769@ARMvm> <20161101224633.4e5ee0ca@utopia> <20161102033552.4d41c9ca@utopia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161102033552.4d41c9ca@utopia> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1381 Lines: 32 On 02/11/16 03:35, Luca Abeni wrote: > On Tue, 1 Nov 2016 22:46:33 +0100 > luca abeni wrote: > [...] > > > > @@ -1074,6 +1161,14 @@ select_task_rq_dl(struct task_struct *p, int cpu, int sd_flag, int flags) > > > > } > > > > rcu_read_unlock(); > > > > > > > > + rq = task_rq(p); > > > > + raw_spin_lock(&rq->lock); > > > > + if (hrtimer_active(&p->dl.inactive_timer)) { > > > > + sub_running_bw(&p->dl, &rq->dl); > > > > + hrtimer_try_to_cancel(&p->dl.inactive_timer); > > > > > > Can't we subtract twice if it happens that after we grabbed rq_lock the timer > > > fired, so it's now waiting for that lock and it goes ahead and sub_running_bw > > > again after we release the lock? > > Uhm... I somehow convinced myself that this could not happen, but I do not > > remember the details, sorry :( > I think I remember the answer now: pi_lock is acquired before invoking select_task_rq > and is released after invoking enqueue_task... So, if there is a pending inactive > timer, its handler will be executed after the task is enqueued... It will see the task > as RUNNING, and will not decrease the active utilisation. > Oh, because we do task_rq_lock() inactive_task_timer(). So, that should save us from the double subtract. Would you mind adding something along the line of what you said above as a comment for next version? Thanks, - Juri