Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754805AbbHDHlZ (ORCPT ); Tue, 4 Aug 2015 03:41:25 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:47091 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752050AbbHDHlY (ORCPT ); Tue, 4 Aug 2015 03:41:24 -0400 Date: Tue, 4 Aug 2015 09:41:16 +0200 From: Peter Zijlstra To: Frederic Weisbecker Cc: 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: <20150804074116.GH25159@twins.programming.kicks-ass.net> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150803173031.GB26022@lerouge> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 789 Lines: 17 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. -- 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/