public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
	linux-kernel@vger.kernel.org, nfont@linux.vnet.ibm.com
Subject: Re: [PATCH v5] workqueue: Fix edge cases for calc of pool's cpumask
Date: Thu, 27 Jul 2017 13:58:35 -0400	[thread overview]
Message-ID: <20170727175834.GG742618@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <47aff1c6-73c2-bc8e-69e9-bdefdb3133c4@linux.vnet.ibm.com>

Hello, Michael.

On Thu, Jul 27, 2017 at 12:06:22PM -0500, Michael Bringmann wrote:
> 
> On NUMA systems with dynamic processors, the content of the cpumask
> may change over time.  As new processors are added via DLPAR operations,
> workqueues are created for them.  Depending upon the order in which CPUs
> are added/removed, we may run into problems with the content of the
> cpumask used by the workqueues.  This patch deals with situations where
> the online cpumask for a node is a proper superset of possible cpumask
> for the node.  It also deals with edge cases where the order in which
> CPUs are removed/added from the online cpumask may leave the set for a
> node empty, and require execution by CPUs on another node.

I think we already talked about this before but can you please note
that this is a bandaid to workaround an underlying bug.  This isn't
something which normally happens on NUMA sytems with dynamic
processors.  This is bandaiding a hole so that the machine at least
doesn't crash immediately until we can get the underlying problem
fixed properly.

Thanks.

-- 
tejun

      reply	other threads:[~2017-07-27 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 17:06 [PATCH v5] workqueue: Fix edge cases for calc of pool's cpumask Michael Bringmann
2017-07-27 17:58 ` 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=20170727175834.GG742618@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwb@linux.vnet.ibm.com \
    --cc=nfont@linux.vnet.ibm.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