[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3861018c-96a2-4055-94ca-39f7a8e631f3@huaweicloud.com>
Date: Mon, 15 Sep 2025 19:18:35 +0800
From: Chen Ridong <chenridong@...weicloud.com>
To: longman@...hat.com, tj@...nel.org, hannes@...xchg.org, mkoutny@...e.com
Cc: cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
lujialin4@...wei.com, chenridong@...wei.com
Subject: Re: [PATCH -next RFC -v2 00/11] Refactor cpus mask setting
On 2025/9/9 11:32, Chen Ridong wrote:
> From: Chen Ridong <chenridong@...wei.com>
>
> 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
>
> ---
>
> Changes from v1:
> - Patch 1: Use direct comparison (cs == &top_cpuset) instead of the
> cpuset_is_root() helper function
> - Patch 6: Updated comments for better clarity
> - Patch 7: Refactored validate_partition to replace the previous
> invalidate_cs_partition implementation
> - Patch 8: Renamed acpus_validate_change to cpus_allowed_validate_change
> - Patch 9: Updated commit message with more detailed information
>
Hi, Longman,
I would be grateful if you could take a look at this series when you have a moment.
--
Best regards,
Ridong
Powered by blists - more mailing lists