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 2D6552C327E; Wed, 17 Sep 2025 20:15:22 +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=1758140123; cv=none; b=O2CIdxHEb1RD/yR3fgw4qb4MF3p6f5UD5P/mK4Ls3gic5WoOMRL4u5EBcS6H+VZu/M2YYQIQbvAWNUvD2djn5+7Rj+ALr5kKc8dMYqE697yaNCcrx4ru67M3nFDbDWISExOw94ofH1nFa7t7HPp6FKcp3hsRFLUzO1iZid0UpQ8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758140123; c=relaxed/simple; bh=oNFa9hwyHgBlCFAoJzpEdMKYbKIFK/L49C59hxmtHA4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=cYeQaIYohTCU5OjEgjcDDwQBgFJENOnZSWehsGtwDPNMAo4KJUvrWjh3O1slxpbd99tv67xDYkSuNbscsFhdeWIhlaLBgmSWA4fst61D8K4nLjU7uPOhNq746uUkwttagOhAofoOAKMhykkJh+jdHgOyIi45r+/uqILqQPtS0lI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=BMiSRl9c; 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="BMiSRl9c" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 86F29C4CEE7; Wed, 17 Sep 2025 20:15:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1758140122; bh=oNFa9hwyHgBlCFAoJzpEdMKYbKIFK/L49C59hxmtHA4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=BMiSRl9cupAEXlLYZ10Y8AkHbXas6DM/97kiiMAA39+cVLoT3at12NXW6WlksxgCA UTxHalJt+Eh6RnrC2YTJp/ftsgRaOnJpA5kJ3r4U+S4pYJRmeo1Qyn5O/Drv4nkbxl vYok7WbvAZAKyECtDa+I2D9T7RGiuIDOQD+vqN1UFNNlNvTNO1M3eRQTPQhHW0RfNs sRraLWuPYupxtDEEa/6xG7hpKyalRZpNB7u1pFOsaa5j6o82ysMK3/1zmKaH2fe2jT dw55dWxbhpnIG3NaKfBt4tSEJQgnhGDfOk2Kg1D7fj9qytu2YMwD2+UQVWmIPfrOOj Mbg/viwphoL6Q== Date: Wed, 17 Sep 2025 10:15:21 -1000 From: Tejun Heo To: Chen Ridong Cc: longman@redhat.com, hannes@cmpxchg.org, mkoutny@suse.com, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, lujialin4@huawei.com, chenridong@huawei.com Subject: Re: [PATCH -next 00/11] Refactor cpus mask setting Message-ID: References: <20250917060454.2885698-1-chenridong@huaweicloud.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: <20250917060454.2885698-1-chenridong@huaweicloud.com> On Wed, Sep 17, 2025 at 06:04:43AM +0000, Chen Ridong wrote: > From: Chen Ridong > > This patch series refactors the CPU mask configuration logic for both > cpuset.cpus and cpuset.cpus.exclusive settings. The primary goal is to > improve code readability through comprehensive function restructuring. > > The CPU mask update process follows these steps: > 1. Parse user input > 2. Skip processing if no actual change to CPU mask > 3. Compute trial cpuset's effective exclusive CPUs > 4. Validate changes and return error if invalid > 5. Handle partition state changes resulting from CPU mask modifications > 6. Apply new CPU mask to the cpuset > 7. Propagate changes through the hierarchy > > The series is organized as follows: > patches 1-3: Code cleanup and preparation for refactoring > patches 4-9: Refactoring of cpuset.cpus configuration logic > patches 10-11: Refactoring of cpuset.cpus.exclusive configuration logic Applied to cgroup/for-6.18. Thanks. -- tejun