From: "xiaofeng.yan" <xiaofeng.yan@huawei.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: <mingo@redhat.com>, <juri.lelli@gmail.com>,
<linux-kernel@vger.kernel.org>, <xiaofeng.yan2012@gmail.com>
Subject: Re: [PATCH] sched/deadline: overrun could happen in start_hrtick_dl
Date: Tue, 8 Jul 2014 19:23:19 +0800 [thread overview]
Message-ID: <53BBD4A7.5050701@huawei.com> (raw)
In-Reply-To: <20140708093334.GD6758@twins.programming.kicks-ass.net>
On 2014/7/8 17:33, Peter Zijlstra wrote:
> On Tue, Jul 08, 2014 at 08:53:27AM +0000, xiaofeng.yan wrote:
>> static void start_hrtick_dl(struct rq *rq, struct task_struct *p)
>> {
>> - s64 delta = p->dl.dl_runtime - p->dl.runtime;
>> -
>> - if (delta > 10000)
>> - hrtick_start(rq, p->dl.runtime);
>> + delta = max_t(s64, 10000LL, delta);
>> + hrtick_start(rq, delta);
>> }
> no, no, no. I said to unify the test.
I understand your idea after reading the next patch. This is good solution.
I will test it with your patch.
> ---
> kernel/sched/core.c | 9 ++++++++-
> kernel/sched/deadline.c | 3 +--
> kernel/sched/fair.c | 7 -------
> 3 files changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index e1a2f31bb0cb..c7b8a6fbac66 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -444,7 +444,14 @@ static void __hrtick_start(void *arg)
> void hrtick_start(struct rq *rq, u64 delay)
> {
> struct hrtimer *timer = &rq->hrtick_timer;
> - ktime_t time = ktime_add_ns(timer->base->get_time(), delay);
> + ktime_t time;
> +
> + /*
> + * Don't schedule slices shorter than 10000ns, that just
> + * doesn't make sense and can cause timer DoS.
> + */
> + delta = max_t(s64, delta, 10000LL);
transfer the argument delta to delay
> + time = ktime_add_ns(timer->base->get_time(), delay);
>
> hrtimer_set_expires(timer, time);
>
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index fc4f98b1258f..e1e24eea8061 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -999,8 +999,7 @@ static void start_hrtick_dl(struct rq *rq, struct task_struct *p)
> {
> s64 delta = p->dl.dl_runtime - p->dl.runtime;
>
> - if (delta > 10000)
> - hrtick_start(rq, p->dl.runtime);
> + hrtick_start(rq, p->dl.runtime);
> }
> #endif
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 923fe32db6b3..713c58d2a7b0 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -3901,13 +3901,6 @@ static void hrtick_start_fair(struct rq *rq, struct task_struct *p)
> return;
> }
>
> - /*
> - * Don't schedule slices shorter than 10000ns, that just
> - * doesn't make sense. Rely on vruntime for fairness.
> - */
> - if (rq->curr != p)
> - delta = max_t(s64, 10000LL, delta);
> -
> hrtick_start(rq, delta);
> }
> }
next prev parent reply other threads:[~2014-07-08 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 8:53 [PATCH] sched/deadline: overrun could happen in start_hrtick_dl xiaofeng.yan
2014-07-08 9:23 ` xiaofeng.yan
2014-07-08 9:33 ` Peter Zijlstra
2014-07-08 9:49 ` Bernd Petrovitsch
2014-07-08 11:23 ` xiaofeng.yan [this message]
2014-07-08 11:50 ` xiaofeng.yan
2014-07-08 12:52 ` Peter Zijlstra
2014-07-09 2:07 ` xiaofeng.yan
-- strict thread matches above, loose matches on Subject: below --
2014-07-08 9:06 xiaofeng.yan
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=53BBD4A7.5050701@huawei.com \
--to=xiaofeng.yan@huawei.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=xiaofeng.yan2012@gmail.com \
/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