From: Peter Zijlstra <peterz@infradead.org>
To: pang.xunlei@zte.com.cn
Cc: juri.lelli@gmail.com, ktkhai@parallels.com,
linux-kernel@vger.kernel.org, mingo@elte.hu, oleg@redhat.com,
pang.xunlei@linaro.org, rostedt@goodmis.org,
umgwanakikbuti@gmail.com
Subject: Re: [RFC][PATCH 1/7] sched: Replace post_schedule with a balance callback list
Date: Wed, 3 Jun 2015 10:55:27 +0200 [thread overview]
Message-ID: <20150603085527.GA3644@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <OF16420525.D7DCA965-ON48257E59.002BFF6E-48257E59.002E24BB@zte.com.cn>
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
On Wed, Jun 03, 2015 at 04:24:05PM +0800, pang.xunlei@zte.com.cn wrote:
> Hi Peter,
>
> This may increase the overhead of schedule() a bit, as it will have
> more work to do.
How so? It replaces the post_schedule() muck and should not be more
expensive than that.
It will make sched_setscheduler() etc.. a little more expensive, but
that doesn't matter, those are not critical things at all.
> check_class_changed():
> if (prev_class->switched_from)
> prev_class->switched_from(rq, p);
> /* Possble rq->lock 'hole'. */
> p->sched_class->switched_to(rq, p);
>
> For above cases, why can't we just add a judgement in switched_to_fair()
> as follows:
> if (rq != task_rq(p))
> return;
Because its too easy to get wrong. There have been many instances of
bugs caused by this dropping of rq->lock.
And sure you can patch it up, once you find it, but I would really
rather prevent these things if at all possible.
next prev parent reply other threads:[~2015-06-03 8:55 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 [this message]
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
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=20150603085527.GA3644@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=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=pang.xunlei@linaro.org \
--cc=pang.xunlei@zte.com.cn \
--cc=rostedt@goodmis.org \
--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