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 C5B9236F430 for ; Tue, 31 Mar 2026 19:12:32 +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=1774984352; cv=none; b=ay/ZRwO6E3xshKNvMpzfPCpLTUuGjdFa9NDp3qXtlD8DrzfIUiMr7xCG1nVo2mSyl3Urq2AFnmET/B7q+mKaIHxEsXnjfZyHGDs6gFQHcNsMYfHvXKcOC1kidx/hK9L9HzmYfB9csj3IidETB+HdRTa4sWoy2gN7ott+Y2URXOQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774984352; c=relaxed/simple; bh=S+fcCsp2zV23IGKMknNkd6khausC2YeO9UYCN3wu+Mw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=TiIYlliDw8pq1ND9MhkI4GcJRRAQaKb2XsWRHC+tEnSQOy7CwiNK2cUo47T0k6cQDEuX6Puvo9yGsZs9ezfGc5UutFaZ2OwN9yhB0OHQt/ENsunCCZBPR054c+e6mDSAyKCLLYHYZNWWRh2OUxOmPuE6LdEz7+kVDaMdZRFpIbk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=iPTdawMi; 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="iPTdawMi" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4DF4FC19423; Tue, 31 Mar 2026 19:12:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774984352; bh=S+fcCsp2zV23IGKMknNkd6khausC2YeO9UYCN3wu+Mw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=iPTdawMivUrUaXfEiFkNBn7tY9E8GR4I+FdVRxihPgOiYi8FN85yu/yEUma5q+kM0 csIdRY5UjUf/KDPBgpNaOE4bQs34I5mSSZrDOHFZxlPifshhYPREMR+gkYML5Wuy03 f9GxxeY7MoHhSs/+YIsjAgJ5jiwFZ5MsINounwE7JMgM00IzeUf24uh1VkCtPsKgiV 6pcDjWtR5XktgXkpI8UfmFEb8uTLCyo968Xws7a2boZhZ+SDSgpY/4JjdRYd4/S0fa XCzvgcmKH8TMYk3KY/ld7QeYnYbXG7w4py/FyXluVoBDshPRSDA7SfCgADRFEKiXrt ouN8PrUHpE+DA== Date: Tue, 31 Mar 2026 09:12:31 -1000 From: Tejun Heo To: Waiman Long Cc: Lai Jiangshan , linux-kernel@vger.kernel.org, Frederic Weisbecker 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=us-ascii Content-Disposition: inline In-Reply-To: <20260331183531.2791465-1-longman@redhat.com> On Tue, Mar 31, 2026 at 02:35:22PM -0400, Waiman Long wrote: > 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 Looks fine to me but imma wait for Frederic's review. Thanks. -- tejun