From: Tejun Heo <tj@kernel.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: torvalds@linux-foundation.org, umgwanakikbuti@gmail.com,
mhocko@kernel.org, tglx@linutronix.de, pmladek@suse.com,
jack@suse.cz, ben@decadent.org.uk, sasha.levin@oracle.com,
shli@fb.com, daniel.bilik@neosystem.cz,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCHSET] workqueue: break local execution guarantee of unbound work items
Date: Wed, 10 Feb 2016 10:57:27 -0500 [thread overview]
Message-ID: <20160210155727.GF3741@mtj.duckdns.org> (raw)
In-Reply-To: <56BAEE62.5030000@suse.cz>
Hello, Jiri.
On Wed, Feb 10, 2016 at 09:01:38AM +0100, Jiri Slaby wrote:
> Thanks all for sorting the issue out. Now it remains to decide what
> should go to stable. Given only 0001 is marked as "Fixes", is that enough?
I think so. The other two are primarily for debugging anyway.
> And what about the vmstat fix:
> commit 176bed1de5bf977938cad26551969eca8f0883b1
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Thu Oct 15 13:01:50 2015 -0700
>
> vmstat: explicitly schedule per-cpu work on the CPU we need it to run on
>
> ? It should fix better than what 0001 is reverting AFAIU, right?
Yes, definitely. Didn't know that one wasn't tagged for stable.
Thanks.
--
tejun
prev parent reply other threads:[~2016-02-10 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 23:14 Tejun Heo
2016-02-09 23:14 ` [PATCH 1/3] Revert "workqueue: make sure delayed work run in local cpu" Tejun Heo
2016-02-15 13:14 ` Michal Hocko
2016-02-09 23:14 ` [PATCH 2/3] workqueue: schedule WORK_CPU_UNBOUND work on wq_unbound_cpumask CPUs Tejun Heo
2016-02-09 23:14 ` [PATCH 3/3] workqueue: implement "workqueue.debug_force_rr_cpu" debug feature Tejun Heo
2016-02-15 13:18 ` Michal Hocko
2016-02-10 0:53 ` [PATCHSET] workqueue: break local execution guarantee of unbound work items Linus Torvalds
2016-02-10 8:01 ` Jiri Slaby
2016-02-10 15:57 ` Tejun Heo [this message]
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=20160210155727.GF3741@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=ben@decadent.org.uk \
--cc=daniel.bilik@neosystem.cz \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jslaby@suse.cz \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=pmladek@suse.com \
--cc=sasha.levin@oracle.com \
--cc=shli@fb.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome