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 3E9A0355F2A for ; Thu, 26 Feb 2026 17:58:16 +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=1772128696; cv=none; b=cByo7RqWSJ/wguj5mex/y8k8zct+0J7z0dmyPZxG969yc2pZfLa1P9GIEQbtqoZUpGAPo4p9WVPraq0fM69Sjscp41tbo8t5Rrov8RT5dsg/lNRFcDXpfkMUuNQsg1yxJ4pBVFKt4zdcMSTjFwdIsgBlse14/bBFqWuyQ9RD+4I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772128696; c=relaxed/simple; bh=qj8tHIfwI3MiIdqv1P4Kx4NRkirCKQwGsRGG74mdGQI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=BcOWy0e0itVx+OiIyW3QK8gV/oByUVBi17FgPoXoqWvDFPfiAZSpMBwmmkHlxipFkMOnUUVThqWShaujIyMFFFioJ4Qjrvia4J+34zbDHWaXfmjzR3Vxey21qLODrZMjKjhtKtuH/f57vpg2+ZcsteS+y7zuN/1oCc3CveCjRp4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=YyEfi6gI; 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="YyEfi6gI" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EE672C116C6; Thu, 26 Feb 2026 17:58:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772128696; bh=qj8tHIfwI3MiIdqv1P4Kx4NRkirCKQwGsRGG74mdGQI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YyEfi6gIQ18cT7EcWXBLTDhk98C/5Sd9t0xzUa6MbRl/tNgoeyBCh73jZSRwyuF8m zQndQH7ZXMZ0PDzgXKfV8xHpmptwXfPtFdKKARZxYfWZdDlD5tLjows8JWdPSvTRVX tG8SCDUZ7WjVQqspJ6BzjJis9ca1xMNADiEo7GadGhOr8UIOtdCdMaZ//bxyReRdgs 3yHY7SBFIgmD8c9MbHjTZosgIE6bg5HorJua6+20mzh/b+g3Fo48rokHj5JhYfgrVz XPMBP3Lk1HDN8nreLVqZx9/pn9qAeOhDK56EOlFORJ87gMcUjonKbSh8l7r6CXaPgE uy0tXJawQZJFA== Date: Thu, 26 Feb 2026 07:58:15 -1000 From: Tejun Heo To: Mallesh Koujalagi Cc: jiangshanlai@gmail.com, peterz@infradead.org, linux-kernel@vger.kernel.org, anshuman.gupta@intel.com, raag.jadav@intel.com Subject: Re: [PATCH] workqueue: Update schedule_work() documentation to reflect per-CPU nature Message-ID: References: <20260226104659.3227091-2-mallesh.koujalagi@intel.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: <20260226104659.3227091-2-mallesh.koujalagi@intel.com> On Thu, Feb 26, 2026 at 04:17:00PM +0530, Mallesh Koujalagi wrote: > The function documentation for schedule_work(), schedule_delayed_work(), > and schedule_delayed_work_on() still described them as using "global" or > "kernel-global" workqueues, which is misleading after commit a2be943b46b4 > ("workqueue: replace use of system_wq with system_percpu_wq"). > > These functions now use system_percpu_wq, which is a per-CPU workqueue > where work items are executed on the CPU where they were queued. Update > the documentation to accurately reflect this CPU affinity behavior. Note that system_wq has always been a percpu workqueue. We've been just renaming things. Nothing wrong with updating documentation but the commit message is misleading. Thanks. -- tejun