mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Fontenot <nfont@linux.vnet.ibm.com>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>,
	Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] workqueue: Fix edge cases for calc of pool's cpumask
Date: Thu, 27 Jul 2017 13:42:16 -0500	[thread overview]
Message-ID: <47ac4fb9-a316-0125-7d4e-73cf602d891e@linux.vnet.ibm.com> (raw)
In-Reply-To: <5c421712-fb38-3020-d3fc-b9bdea792cd3@linux.vnet.ibm.com>

On 07/27/2017 01:15 PM, 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.
> 
> In these and other cases, the patch attempts to ensure that a valid,
> usable cpumask is used to set up newly created pools for workqueues.
> This patch provides a fix for NUMA systems which can add/subtract
> processors dynamically.  The patch is expected to be an intermediate
> one while developers search for any underlying issues.
> 
> [With additions to the patch provided by Tejun Hao <tj@kernel.org>]
> 
> Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
> ---
> Changes in V6:
>   -- Update descriptive text
> ---
>  kernel/workqueue.c |    7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index c74bf39..6b6d540 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -3577,6 +3577,13 @@ static bool wq_calc_node_cpumask(const struct workqueue_attrs *attrs, int node,
> 
>  	/* yeap, return possible CPUs in @node that @attrs wants */
>  	cpumask_and(cpumask, attrs->cpumask, wq_numa_possible_cpumask[node]);
> +
> +	if (cpumask_empty(cpumask)) {
> +		pr_warn_once("WARNING: workqueue cpumask: onl intersect > "
                                                          ^^^
This message doesn't seem right, or I am missing something, "onl"?

-Nathan

> +				"possible intersect\n");
> +		return false;
> +	}
> +
>  	return !cpumask_equal(cpumask, attrs->cpumask);
> 
>  use_dfl:
> 

  parent reply	other threads:[~2017-07-27 18:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 18:15 Michael Bringmann
2017-07-27 18:31 ` Tejun Heo
2017-07-27 19:07   ` Michael Bringmann
2017-07-27 19:24     ` Tejun Heo
2017-07-27 20:15       ` Michael Bringmann
2017-07-27 20:46         ` Tejun Heo
2017-07-27 18:42 ` Nathan Fontenot [this message]
2017-07-27 19:12   ` Michael Bringmann
2017-07-27 19:24     ` 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=47ac4fb9-a316-0125-7d4e-73cf602d891e@linux.vnet.ibm.com \
    --to=nfont@linux.vnet.ibm.com \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwb@linux.vnet.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®