From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH wq/for-4.5-fixes] workqueue: handle NUMA_NO_NODE for unbound pool_workqueue lookup
Date: Thu, 04 Feb 2016 04:15:28 +0100 [thread overview]
Message-ID: <1454555728.3677.34.camel@gmail.com> (raw)
In-Reply-To: <20160203185523.GL14091@mtj.duckdns.org>
On Wed, 2016-02-03 at 13:55 -0500, Tejun Heo wrote:
> On Wed, Feb 03, 2016 at 01:54:25PM -0500, Tejun Heo wrote:
> > Fix it by mapping NUMA_NO_NODE to the default pool_workqueue from
> > unbound_pwq_by_node(). This is a temporary workaround. The long
> > term
> > solution is keeping CPU -> NODE mapping stable across CPU
> > off/online
> > cycles which is in the works.
>
> Forgot to mention. Can you please test this? Once verified, I'll
> route it through wq/for-4.5-fixes.
I've passed it on, hopefully the user can make time to test.
-Mike
next prev parent reply other threads:[~2016-02-04 3:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 14:44 mod_delayed_work() explosion due to 874bbfe6 Mike Galbraith
2016-02-03 14:37 ` Michal Hocko
2016-02-03 16:32 ` Tejun Heo
2016-02-03 18:54 ` [PATCH wq/for-4.5-fixes] workqueue: handle NUMA_NO_NODE for unbound pool_workqueue lookup Tejun Heo
2016-02-03 18:55 ` Tejun Heo
2016-02-04 3:15 ` Mike Galbraith [this message]
2016-02-03 19:12 ` Thomas Gleixner
2016-02-03 19:28 ` Tejun Heo
2016-02-04 2:12 ` Mike Galbraith
2016-02-04 8:40 ` Michal Hocko
2016-02-10 15:55 ` Tejun Heo
2016-02-15 17:33 ` Michal Hocko
2016-02-15 18:21 ` Tejun Heo
2016-02-15 20:54 ` Michal Hocko
2016-02-15 21:02 ` 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=1454555728.3677.34.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.