From: Peter Zijlstra <peterz@infradead.org>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@arm.com>,
Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
Luca Abeni <luca.abeni@santannapisa.it>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline
Date: Mon, 13 Feb 2017 12:12:29 +0100 [thread overview]
Message-ID: <20170213111229.GH6500@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <a11b216b344a7ccdf7e3c89a6c8617bb446b91f7.1486754348.git.bristot@redhat.com>
On Fri, Feb 10, 2017 at 08:48:11PM +0100, Daniel Bristot de Oliveira wrote:
> +/* During the activation, CBS checks if it can reuse the current task's
> + * runtime and period. If the deadline of the task is in the past, CBS
Broken comment style, fixed that for you.
next prev parent reply other threads:[~2017-02-13 11:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 19:48 [PATCH 0/2] sched/deadline: Fixes for constrained deadline tasks Daniel Bristot de Oliveira
2017-02-10 19:48 ` [PATCH 1/2] sched/deadline: Replenishment timer should fire in the next period Daniel Bristot de Oliveira
2017-02-10 21:47 ` Steven Rostedt
2017-02-11 7:12 ` luca abeni
2017-02-13 11:10 ` Peter Zijlstra
2017-02-13 14:59 ` Steven Rostedt
2017-02-13 15:35 ` Juri Lelli
2017-02-10 19:48 ` [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Daniel Bristot de Oliveira
2017-02-11 7:15 ` luca abeni
2017-02-11 8:00 ` Mike Galbraith
2017-02-11 14:35 ` Steven Rostedt
2017-02-13 11:12 ` Peter Zijlstra
2017-02-13 11:12 ` Peter Zijlstra [this message]
2017-02-13 13:16 ` Daniel Bristot de Oliveira
2017-02-13 15:33 ` Steven Rostedt
2017-02-13 15:46 ` Daniel Bristot de Oliveira
2017-02-13 16:21 ` Daniel Bristot de Oliveira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170213111229.GH6500@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tommaso.cucinotta@sssup.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox