From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753394AbdBMPdQ (ORCPT ); Mon, 13 Feb 2017 10:33:16 -0500 Received: from mail.kernel.org ([198.145.29.136]:58514 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750943AbdBMPdN (ORCPT ); Mon, 13 Feb 2017 10:33:13 -0500 Date: Mon, 13 Feb 2017 10:33:03 -0500 From: Steven Rostedt To: Daniel Bristot de Oliveira Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Peter Zijlstra , Juri Lelli , Tommaso Cucinotta , Luca Abeni Subject: Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Message-ID: <20170213103303.0e3b3953@gandalf.local.home> In-Reply-To: References: X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 10 Feb 2017 20:48:11 +0100 Daniel Bristot de Oliveira wrote: > > +static inline bool dl_is_constrained(struct sched_dl_entity *dl_se) > +{ > + return dl_se->dl_runtime < dl_se->dl_period; > +} > + Is it ever appropriate for a dl task to have runtime == period? What purpose would that serve? Just run the task as FIFO higher than everything else. Or was this suppose to be dl_deadline < dl_period? -- Steve