From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Lai Jiangshan <jiangshanlai@gmail.com>
Subject: [GIT PULL] workqueue changes for v4.16-rc1
Date: Tue, 30 Jan 2018 10:11:35 -0800 [thread overview]
Message-ID: <20180130181135.GG1121507@devbig577.frc2.facebook.com> (raw)
Hello, Linus.
Workqueue changes for v4.16-rc1. Two patches for the following.
* Workqueue has an early init trick where workqueues can be created
and work items queued on them before the workqueue subsystem is
online. This helps simplifying early init and operation of low
level subsystems which use workqueues for managerial things which
aren't depended upon early during boot.
Out of laziness, the early init didn't cover workqueues with
WQ_MEM_RECLAIM, which is inconsistent and confusing because adding
the flag simply makes the system fail to boot. Cover WQ_MEM_RECLAIM
too.
This was originally brought up for RCU but RCU didn't actually need
this. I still think it's a good idea to cover it.
Thanks.
The following changes since commit b2cd1df66037e7c4697c7e40496bf7e4a5e16a2d:
Linux 4.15-rc7 (2018-01-07 14:22:41 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-4.16
for you to fetch changes up to 40c17f75dfa9ec163478efd3f7443fd6af9992c9:
workqueue: allow WQ_MEM_RECLAIM on early init workqueues (2018-01-08 05:38:37 -0800)
----------------------------------------------------------------
Tejun Heo (2):
workqueue: separate out init_rescuer()
workqueue: allow WQ_MEM_RECLAIM on early init workqueues
kernel/workqueue.c | 64 ++++++++++++++++++++++++++++++++++--------------------
1 file changed, 40 insertions(+), 24 deletions(-)
--
tejun
reply other threads:[~2018-01-30 18:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180130181135.GG1121507@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome