From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EA9FBC433E0 for ; Tue, 12 Jan 2021 17:53:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9B816222F9 for ; Tue, 12 Jan 2021 17:53:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2392260AbhALRxj (ORCPT ); Tue, 12 Jan 2021 12:53:39 -0500 Received: from foss.arm.com ([217.140.110.172]:50476 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390631AbhALRxj (ORCPT ); Tue, 12 Jan 2021 12:53:39 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 8CBB91042; Tue, 12 Jan 2021 09:52:53 -0800 (PST) Received: from e113632-lin (e113632-lin.cambridge.arm.com [10.1.194.46]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 049213F66E; Tue, 12 Jan 2021 09:52:51 -0800 (PST) From: Valentin Schneider To: Lai Jiangshan , Peter Zijlstra Cc: Thomas Gleixner , LKML , Qian Cai , Vincent Donnefort , Dexuan Cui , Lai Jiangshan , Paul McKenney , Vincent Guittot , Steven Rostedt , Jens Axboe Subject: Re: [PATCH -tip V3 0/8] workqueue: break affinity initiatively In-Reply-To: References: <20201226025117.2770-1-jiangshanlai@gmail.com> <87o8hv7pnd.fsf@nanos.tec.linutronix.de> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/26.3 (x86_64-pc-linux-gnu) Date: Tue, 12 Jan 2021 17:52:46 +0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/01/21 12:33, Lai Jiangshan wrote: >> I thought only pcpu pools would get the POOL_DISASSOCIATED flag on >> offline, but it seems unbound pools also get it at init time. Did I get >> that right? > > You are right. > > The POOL_DISASSOCIATED flag indicates whether the pool is concurrency > management or not (negative way, POOL_DISASSOCIATED means "not concurrency > management"). So it should be applied for all unbound pools. > > When !POOL_DISASSOCIATED means it is a percpu pool, and the pool->cpu > is online and the offline callback has not been called yet even the pool->cpu > is going to be offline. So !POOL_DISASSOCIATED is used a lot in the code. Thanks!