Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932164AbbGPTYx (ORCPT ); Thu, 16 Jul 2015 15:24:53 -0400 Received: from mail-yk0-f195.google.com ([209.85.160.195]:33004 "EHLO mail-yk0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751968AbbGPTYw (ORCPT ); Thu, 16 Jul 2015 15:24:52 -0400 Date: Thu, 16 Jul 2015 15:24:48 -0400 From: Tejun Heo To: Daniel Bristot de Oliveira Cc: LKML , Lai Jiangshan , Frederic Weisbecker , Rik van Riel , "Luis Claudio R. Goncalves" Subject: Re: [RFC] workqueue: avoiding unbounded wq on isolated CPUs by default Message-ID: <20150716192448.GY15934@mtj.duckdns.org> References: <9e53de7c91c885ee255e16ee25f401d9eedf08d9.1437067317.git.bristot@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9e53de7c91c885ee255e16ee25f401d9eedf08d9.1437067317.git.bristot@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 702 Lines: 20 Hello, On Thu, Jul 16, 2015 at 04:16:23PM -0300, Daniel Bristot de Oliveira wrote: > By default, unbounded workqueues run on all CPUs, which includes > isolated CPUs. This patch avoids unbounded workqueues running on > isolated CPUs by default, keeping the current behavior when no > CPUs were isolated. I don't have a strong opinion about this. Frederic, was there a reason we didn't do this when we added cpumasks for unbound wq's? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/