From: Peter Zijlstra <peterz@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Ulrich Obergfell <uobergfe@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, kernel-team@fb.com,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, rmk+kernel@arm.linux.org.uk,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] workqueue: warn if memory reclaim tries to flush !WQ_MEM_RECLAIM workqueue
Date: Fri, 29 Jan 2016 16:17:39 +0100 [thread overview]
Message-ID: <20160129151739.GA1087@worktop> (raw)
In-Reply-To: <20160129110941.GK32380@htj.duckdns.org>
On Fri, Jan 29, 2016 at 06:09:41AM -0500, Tejun Heo wrote:
> I posted a patch to disable
> disable flush dependency checks on those workqueues and there's a
> outreachy project to weed out the users of the old interface, so
> hopefully this won't be an issue soon.
Will that same project review all workqueue users for the strict per-cpu
stuff, so we can finally kill that weird stuff you do on hotplug?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-01-29 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151203002810.GJ19878@mtj.duckdns.org>
[not found] ` <20151203093350.GP17308@twins.programming.kicks-ass.net>
[not found] ` <20151203100018.GO11639@twins.programming.kicks-ass.net>
[not found] ` <20151203144811.GA27463@mtj.duckdns.org>
[not found] ` <20151203150442.GR17308@twins.programming.kicks-ass.net>
[not found] ` <20151203150604.GC27463@mtj.duckdns.org>
[not found] ` <20151203192616.GJ27463@mtj.duckdns.org>
[not found] ` <20160126173843.GA11115@ulmo.nvidia.com>
[not found] ` <20160128101210.GC6357@twins.programming.kicks-ass.net>
2016-01-29 11:09 ` [PATCH] workqueue: warn if memory reclaim tries to flush !WQ_MEM_RECLAIM workqueue Tejun Heo
2016-01-29 15:17 ` Peter Zijlstra [this message]
2016-01-29 18:28 ` 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=20160129151739.GA1087@worktop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jonathanh@nvidia.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=thierry.reding@gmail.com \
--cc=tj@kernel.org \
--cc=uobergfe@redhat.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).