From: Christoph Lameter <cl@linux.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>, Shaohua Li <shli@fb.com>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [GIT PULL] workqueue fixes for v4.3-rc5
Date: Wed, 14 Oct 2015 13:03:38 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1510141301340.13301@east.gentwo.org> (raw)
In-Reply-To: <CA+55aFzV61qsWOObLUPpL-2iU1=8EopEgfse+kRGuUi9kevoOA@mail.gmail.com>
On Wed, 14 Oct 2015, Linus Torvalds wrote:
> On Tue, Oct 13, 2015 at 2:49 PM, Tejun Heo <tj@kernel.org> wrote:
> >
> > Single patch to fix delayed work being queued on the wrong CPU. This
> > has been broken forever (v2.6.31+) but obviously doesn't trigger in
> > most configurations.
>
> So why is this a bugfix? If cpu == WORK_CPU_UNBOUND, then things
> _shouldn't_ care which cpu it gets run on.
UNBOUND means not fixed to a processor. The system should have
freedom to schedule unbound work requests anywhere it wants. This is
something we also want for the NOHZ work in order to move things like
these workqueue items to processors that are not supposed to be low
latency.
--
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:[~2015-10-14 18:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151013214952.GB23106@mtj.duckdns.org>
2015-10-14 16:30 ` Linus Torvalds
2015-10-14 16:57 ` Tejun Heo
2015-10-14 17:36 ` Linus Torvalds
2015-10-14 17:57 ` Christoph Lameter
2015-10-14 18:37 ` Linus Torvalds
2015-10-14 18:58 ` Christoph Lameter
2015-10-14 19:01 ` Linus Torvalds
2015-10-14 19:02 ` Tejun Heo
2015-10-14 19:16 ` Linus Torvalds
2015-10-14 19:38 ` Tejun Heo
2015-10-14 20:10 ` Linus Torvalds
2015-10-14 20:24 ` Tejun Heo
2015-10-19 3:51 ` Mike Galbraith
2015-10-16 19:51 ` [PATCH] vmstat_update: ensure work remains on the same core Chris Metcalf
2015-10-16 19:54 ` Linus Torvalds
2015-10-14 18:03 ` Christoph Lameter [this message]
2015-10-14 18:40 ` [GIT PULL] workqueue fixes for v4.3-rc5 Linus Torvalds
2015-10-14 18:59 ` Christoph Lameter
2015-10-14 19:10 ` Linus Torvalds
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=alpine.DEB.2.20.1510141301340.13301@east.gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=shli@fb.com \
--cc=tj@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