Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754138AbbHJORF (ORCPT ); Mon, 10 Aug 2015 10:17:05 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:33554 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751554AbbHJORA (ORCPT ); Mon, 10 Aug 2015 10:17:00 -0400 Date: Mon, 10 Aug 2015 16:16:58 +0200 From: Frederic Weisbecker To: Juri Lelli Cc: Peter Zijlstra , LKML , Thomas Gleixner , Preeti U Murthy , Christoph Lameter , Ingo Molnar , Viresh Kumar , Rik van Riel Subject: Re: [PATCH 07/10] sched: Migrate sched to use new tick dependency mask model Message-ID: <20150810141656.GA31251@lerouge> References: <1437669735-8786-1-git-send-email-fweisbec@gmail.com> <1437669735-8786-8-git-send-email-fweisbec@gmail.com> <20150803140046.GK19282@twins.programming.kicks-ass.net> <20150803145031.GD25554@lerouge> <20150803170911.GV25159@twins.programming.kicks-ass.net> <20150803173031.GB26022@lerouge> <20150804074116.GH25159@twins.programming.kicks-ass.net> <55C8AEDC.90603@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55C8AEDC.90603@arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1553 Lines: 33 On Mon, Aug 10, 2015 at 03:02:04PM +0100, Juri Lelli wrote: > Hi, > > On 04/08/15 08:41, Peter Zijlstra wrote: > > On Mon, Aug 03, 2015 at 07:30:32PM +0200, Frederic Weisbecker wrote: > >>> But you've forgotten about SCHED_DEADLINE, we count those in: > >>> rq->dl.dl_nr_running. > >> > >> Indeed. Hmm, there is no preemption between SCHED_DEALINE tasks, right? > >> So I can treat it like SCHED_FIFO. > > > > Sadly no. Even though EDF has static job priority (once a job is > > activated its priority doesn't change anymore) DEADLINE also has a CBS > > component and that needs the tick regardless, even with a single task. > > > > So any deadline task running means we cannot stop the tick. > > Well, couldn't we stop it when we use hrtick? As start_hrtick_dl() sets > the hrtick to fire at tasks runtime depletion instant. Hrtick() only does the task tick part of scheduler_tick(). There are many other things that need to be updated. Cpu load active (which is buggy with full dynticks btw. because __update_cpu_load() expects nothing else than regular frequency updates or idle decay. There is also calc_global_load(), load balancing stuffs. I considered many times relying on hrtick btw but everyone seem to say it has a lot of overhead, especially due to clock reprogramming on schedule() calls. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/