From: Peter Zijlstra <peterz@infradead.org>
To: Joonwoo Park <joonwoop@codeaurora.org>
Cc: Srivatsa Vaddagiri <vatsa@codeaurora.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: Fix SCHED_HRTICK bug leading to late preemption of tasks
Date: Mon, 19 Sep 2016 10:21:58 +0200 [thread overview]
Message-ID: <20160919082158.GS5016@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1474075731-11550-1-git-send-email-joonwoop@codeaurora.org>
On Fri, Sep 16, 2016 at 06:28:51PM -0700, Joonwoo Park wrote:
> From: Srivatsa Vaddagiri <vatsa@codeaurora.org>
>
> SCHED_HRTICK feature is useful to preempt SCHED_FAIR tasks on-the-dot
Right, but I always found the overhead of the thing too high to be
really useful.
How come you're using this?
> joonwoop: Do we also need to update or remove if-statement inside
> hrtick_update()?
> I guess not because hrtick_update() doesn't want to start hrtick when cfs_rq
> has large number of nr_running where slice is longer than sched_latency.
Right, you want that to match with whatever sched_slice() does.
> +++ b/kernel/sched/fair.c
> @@ -4458,7 +4458,7 @@ static void hrtick_start_fair(struct rq *rq, struct task_struct *p)
>
> WARN_ON(task_rq(p) != rq);
>
> - if (cfs_rq->nr_running > 1) {
> + if (rq->cfs.h_nr_running > 1) {
> u64 slice = sched_slice(cfs_rq, se);
> u64 ran = se->sum_exec_runtime - se->prev_sum_exec_runtime;
> s64 delta = slice - ran;
Yeah, that looks right. I don't think I've ever tried hrtick with
cgroups enabled...
next prev parent reply other threads:[~2016-09-19 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 1:28 [PATCH] sched: Fix SCHED_HRTICK bug leading to late preemption of tasks Joonwoo Park
2016-09-17 23:28 ` Wanpeng Li
2016-09-19 18:08 ` Joonwoo Park
2016-09-19 23:30 ` Wanpeng Li
2016-09-19 8:21 ` Peter Zijlstra [this message]
2016-09-19 18:04 ` Joonwoo Park
2016-09-19 18:17 ` Joonwoo Park
2016-09-22 14:01 ` [tip:sched/core] sched/fair: " tip-bot for Srivatsa Vaddagiri
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=20160919082158.GS5016@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=joonwoop@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=vatsa@codeaurora.org \
/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;
as well as URLs for NNTP newsgroup(s).