From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 12CC944B67E for ; Tue, 31 Mar 2026 21:26:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774992400; cv=none; b=buP/90LaUiOObvhp2M8KtCZCv2bhYhoIEEvKm7XhPseMk28FILRIpUdctvThzClj6ycydxMftRTnKCU8zrd4RGHrDotwnrYYmHrV1quh+WDcCU+5YrBOhOpSwRiyRdSrVxBqu86/E+DDZzIcVlP+Xw4qXIr/K4ctYIClBV5kFWE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774992400; c=relaxed/simple; bh=sPPhn11BXXiscAgTTzSuSjemxDip4A96LV+i4Q74I60=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=N3r8Hn5LWCsaE7ajIbvjht7iu6T9qqqjJtePXtSvHO2EKrkZ9Pd/gZ7l1obF4Mgr1pv6mo2MX5Zx0lmJM+T0Kvjjprw/ikeTDxV5MrONKqCzTdO4EYB/8dJT/u1GXb90cJHSi29v2B/d7l336CgWSDKdE7iD7hKN1Q2g/hA+cBM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=PukyZLys; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="PukyZLys" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 46355C19423; Tue, 31 Mar 2026 21:26:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774992399; bh=sPPhn11BXXiscAgTTzSuSjemxDip4A96LV+i4Q74I60=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=PukyZLysA2OZW1qn7/k+uwaYmDuXc3u6aGY4TZz8nCNNHw9OgoNHQuJiePEVVEi/f mkRnpGjoVeXZC8+LhJpugfSKP1pWE8z/+x8c3NNZj1rEC7AFAK2YFgU+9bGyfAQe6j oqNw06qMNZ7WkcxfBcnBGjgw1us98OBwTts+dSX7W+CI1OPdoOt6KNR6Cd9XRr0TPx JeVq642FS7qG+YdBbbevpCiDJdEcs38RDrsRES0lfB17ayLG4LCx4plql08WFcog9Y vLbN8vYDvnbVY3LlSPyVW7i6ICIWTm84RS1mZIIKMpfpHotzooXrfFq9fTD3cVFftu gleAyVYIRktwA== Date: Tue, 31 Mar 2026 23:26:36 +0200 From: Frederic Weisbecker To: Waiman Long Cc: Tejun Heo , Lai Jiangshan , linux-kernel@vger.kernel.org Subject: Re: [PATCH] workqueue: Remove HK_TYPE_WQ from affecting wq_unbound_cpumask Message-ID: References: <20260331183531.2791465-1-longman@redhat.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20260331183531.2791465-1-longman@redhat.com> Le Tue, Mar 31, 2026 at 02:35:22PM -0400, Waiman Long a écrit : > For historical reason, wq_unbound_cpumask is initially set as > intersection of HK_TYPE_DOMAIN, HK_TYPE_WQ and workqueue.unbound_cpus > boot command line option. > > At run time, users can update the unbound cpumask via the > /sys/devices/virtual/workqueue/cpumask sysfs file. Creation > and modification of cpuset isolated partitions will also update > wq_unbound_cpumask based on the latest HK_TYPE_DOMAIN cpumask. > The HK_TYPE_WQ cpumask is out of the picture with these runtime updates. > > Complete the transition by taking HK_TYPE_WQ out from the workqueue code > and make it depends on HK_TYPE_DOMAIN only from the housekeeping side. > The final goal is to eliminate HK_TYPE_WQ as a housekeeping cpumask type. > > Signed-off-by: Waiman Long Acked-by: Frederic Weisbecker -- Frederic Weisbecker SUSE Labs