Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1579869
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline |
| Date | 2017-02-13 16:40 +0100 |
| Message-ID | <taqTo-5xK-43@gated-at.bofh.it> (permalink) |
| References | <t9pmF-7LY-1@gated-at.bofh.it> <t9pmG-7LY-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 10 Feb 2017 20:48:11 +0100
Daniel Bristot de Oliveira <bristot@redhat.com> 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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 0/2] sched/deadline: Fixes for constrained deadline tasks Daniel Bristot de Oliveira <bristot@redhat.com> - 2017-02-10 20:50 +0100
[PATCH 1/2] sched/deadline: Replenishment timer should fire in the next period Daniel Bristot de Oliveira <bristot@redhat.com> - 2017-02-10 20:50 +0100
Re: [PATCH 1/2] sched/deadline: Replenishment timer should fire in the next period Steven Rostedt <rostedt@goodmis.org> - 2017-02-10 22:50 +0100
Re: [PATCH 1/2] sched/deadline: Replenishment timer should fire in the next period luca abeni <luca.abeni@santannapisa.it> - 2017-02-11 08:20 +0100
Re: [PATCH 1/2] sched/deadline: Replenishment timer should fire in the next period Peter Zijlstra <peterz@infradead.org> - 2017-02-13 12:20 +0100
Re: [PATCH 1/2] sched/deadline: Replenishment timer should fire in the next period Steven Rostedt <rostedt@goodmis.org> - 2017-02-13 16:10 +0100
Re: [PATCH 1/2] sched/deadline: Replenishment timer should fire in the next period Juri Lelli <juri.lelli@arm.com> - 2017-02-13 16:40 +0100
[PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Daniel Bristot de Oliveira <bristot@redhat.com> - 2017-02-10 20:50 +0100
Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline luca abeni <luca.abeni@santannapisa.it> - 2017-02-11 08:20 +0100
Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Mike Galbraith <efault@gmx.de> - 2017-02-11 09:10 +0100
Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Steven Rostedt <rostedt@goodmis.org> - 2017-02-11 15:40 +0100
Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Peter Zijlstra <peterz@infradead.org> - 2017-02-13 12:20 +0100
Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Peter Zijlstra <peterz@infradead.org> - 2017-02-13 12:20 +0100
Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Daniel Bristot de Oliveira <bristot@redhat.com> - 2017-02-13 14:20 +0100
Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Steven Rostedt <rostedt@goodmis.org> - 2017-02-13 16:40 +0100
Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Daniel Bristot de Oliveira <bristot@redhat.com> - 2017-02-13 17:00 +0100
Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Daniel Bristot de Oliveira <bristot@redhat.com> - 2017-02-13 17:30 +0100
csiph-web