From: Tejun Heo <tj@kernel.org>
To: mingo@elte.hu, peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCHSET sched/core] sched: prepare for cmwq
Date: Thu, 13 May 2010 12:48:21 +0200 [thread overview]
Message-ID: <1273747705-7829-1-git-send-email-tj@kernel.org> (raw)
Hello, Ingo, Peter.
These four patches are the scheduler modifications necessary for cmwq
and contains the following four patches.
0001-sched-consult-online-mask-instead-of-active-in-selec.patch
0002-sched-implement-__set_cpus_allowed.patch
0003-sched-refactor-try_to_wake_up.patch
0004-sched-add-hooks-for-workqueue.patch
The first three have been posted multiple times as part of cmwq
patchset multiple times. Other than description updates to explain
why they are needed, these three patches haven't changed from the last
posting[L].
The last patch adds two hardcoded workqueue hooks as suggested in in
the unify-tracers-in-sched thread[U]. These new hardcoded hooks are
much simpler and no scheduler behavior change is leaked outside of
sched.c. Workqueue workers are marked with PF_WQ_WORKER and hooks are
called only for them. Instead of exporting try_to_wake_up_local(),
the sleeping hook now returns a pointer to local task which is woken
up by scheduler. The hooks are defined as noop for now and will be
filled later by cmwq implementation.
The change from sched_notifier to the hardcoded hooks doesn't make any
notable difference to cmwq implementation itself.
This patchset is available in the following git tree.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git sched-wq
and contains the following changes.
include/linux/sched.h | 15 ++-
kernel/fork.c | 2
kernel/sched.c | 191 +++++++++++++++++++++++++++++++++--------------
kernel/workqueue_sched.h | 16 +++
4 files changed, 163 insertions(+), 61 deletions(-)
Thanks.
--
tejun
[L] http://thread.gmane.org/gmane.linux.kernel/954759
[U] http://thread.gmane.org/gmane.linux.kernel/980857
next reply other threads:[~2010-05-13 10:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 10:48 Tejun Heo [this message]
2010-05-13 10:48 ` [PATCH 1/4] sched: consult online mask instead of active in select_fallback_rq() Tejun Heo
2010-05-31 8:01 ` Peter Zijlstra
2010-05-31 9:48 ` Tejun Heo
2010-05-13 10:48 ` [PATCH 2/4] sched: implement __set_cpus_allowed() Tejun Heo
2010-05-31 8:01 ` Peter Zijlstra
2010-05-31 9:55 ` Tejun Heo
2010-05-31 10:01 ` Peter Zijlstra
2010-05-31 10:02 ` Peter Zijlstra
2010-05-31 10:06 ` Tejun Heo
2010-05-31 10:15 ` Peter Zijlstra
2010-05-31 10:19 ` Tejun Heo
2010-05-31 10:46 ` Peter Zijlstra
2010-05-31 11:47 ` Tejun Heo
2010-05-13 10:48 ` [PATCH 3/4] sched: refactor try_to_wake_up() Tejun Heo
2010-05-13 10:48 ` [PATCH 4/4] sched: add hooks for workqueue Tejun Heo
2010-05-31 8:01 ` Peter Zijlstra
2010-05-31 9:58 ` Tejun Heo
2010-05-31 10:05 ` Peter Zijlstra
2010-05-31 10:07 ` Tejun Heo
2010-05-17 23:13 ` [PATCHSET sched/core] sched: prepare for cmwq Tejun Heo
2010-05-21 13:25 ` Tejun Heo
2010-05-23 9:05 ` Ingo Molnar
2010-05-23 9:08 ` Tejun Heo
2010-05-23 9:13 ` Ingo Molnar
2010-05-23 9:24 ` Tejun Heo
2010-05-23 10:20 ` Ingo Molnar
2010-05-23 10:26 ` Tejun Heo
2010-05-27 8:26 ` Tejun Heo
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=1273747705-7829-1-git-send-email-tj@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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).