From: Peter Zijlstra <peterz@infradead.org>
To: Kirill Tkhai <tkhai@yandex.ru>
Cc: "umgwanakikbuti@gmail.com" <umgwanakikbuti@gmail.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"ktkhai@parallels.com" <ktkhai@parallels.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"juri.lelli@gmail.com" <juri.lelli@gmail.com>,
"pang.xunlei@linaro.org" <pang.xunlei@linaro.org>,
"oleg@redhat.com" <oleg@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"luca.abeni@unitn.it" <luca.abeni@unitn.it>
Subject: Re: [RFC][PATCH 3/7] sched: Allow balance callbacks for check_class_changed()
Date: Wed, 3 Jun 2015 12:45:34 +0200 [thread overview]
Message-ID: <20150603104534.GB3644@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <226151433328161@web20o.yandex.ru>
On Wed, Jun 03, 2015 at 01:42:41PM +0300, Kirill Tkhai wrote:
> [resend]
>
> 03.06.2015, 10:32, "Peter Zijlstra" <peterz@infradead.org>:
> > On Tue, Jun 02, 2015 at 07:27:19PM +0300, Kirill Tkhai wrote:
> >>> + * task_dead_dl() will cancel our timer if we happen to die while
> >>> + * its still pending.
> >> task_dead_dl() is called for tasks of deadline class only. So if we do that,
> >> the timer may be executed after final task's dead.
> >
> > Indeed; sleep deprived brain misses the obvious :/
>
> I have an idea, but it require small hrtimer modification. We may use
> task_struct counters {get,put}_task_struct(), when we're starting or cancelling
> the timer, and in timer handler. But it require to return back the commit:
Yeah, already working on that. :-)
next prev parent reply other threads:[~2015-06-03 10:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 13:58 [RFC][PATCH 0/7] sched: balance callbacks Peter Zijlstra
2015-06-01 13:58 ` [RFC][PATCH 1/7] sched: Replace post_schedule with a balance callback list Peter Zijlstra
2015-06-03 4:41 ` Kamalesh Babulal
2015-06-03 7:21 ` Peter Zijlstra
2015-06-03 8:24 ` pang.xunlei
2015-06-03 8:55 ` Peter Zijlstra
2015-06-05 7:13 ` pang.xunlei
2015-06-05 7:19 ` Peter Zijlstra
2015-06-01 13:58 ` [RFC][PATCH 2/7] sched: Use replace normalize_task() with __sched_setscheduler() Peter Zijlstra
2015-06-01 13:58 ` [RFC][PATCH 3/7] sched: Allow balance callbacks for check_class_changed() Peter Zijlstra
2015-06-02 13:58 ` Kirill Tkhai
2015-06-02 14:27 ` Peter Zijlstra
2015-06-02 16:07 ` Peter Zijlstra
2015-06-02 16:27 ` Kirill Tkhai
2015-06-03 7:32 ` Peter Zijlstra
2015-06-03 10:40 ` Kirill Tkhai
2015-06-03 10:42 ` Kirill Tkhai
2015-06-03 10:45 ` Peter Zijlstra [this message]
2015-06-01 13:58 ` [RFC][PATCH 4/7] sched,rt: Remove return value from pull_rt_task() Peter Zijlstra
2015-06-01 13:58 ` [RFC][PATCH 5/7] sched,rt: Convert switched_{from,to}_rt() / prio_changed_rt() to balance callbacks Peter Zijlstra
2015-06-01 13:58 ` [RFC][PATCH 6/7] sched,dl: Remove return value from pull_dl_task() Peter Zijlstra
2015-06-01 13:58 ` [RFC][PATCH 7/7] sched,dl: Convert switched_{from,to}_dl() / prio_changed_dl() to balance callbacks Peter Zijlstra
2015-06-03 4:52 ` Kamalesh Babulal
2015-06-01 14:16 ` [RFC][PATCH 0/7] sched: " Peter Zijlstra
2015-06-01 14:42 ` Mike Galbraith
2015-06-02 6:48 ` Mike Galbraith
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=20150603104534.GB3644@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=juri.lelli@gmail.com \
--cc=ktkhai@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=pang.xunlei@linaro.org \
--cc=rostedt@goodmis.org \
--cc=tkhai@yandex.ru \
--cc=umgwanakikbuti@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;
as well as URLs for NNTP newsgroup(s).