mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Chen Ridong <chenridong@huaweicloud.com>
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
Date: Wed, 17 Sep 2025 10:15:21 -1000	[thread overview]
Message-ID: <aMsW2WGWrZUm5Qee@slm.duckdns.org> (raw)
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 <chenridong@huawei.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

Applied to cgroup/for-6.18.

Thanks.

-- 
tejun

      parent reply	other threads:[~2025-09-17 20:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  6:04 Chen Ridong
2025-09-17  6:04 ` [PATCH -next 01/11] cpuset: move the root cpuset write check earlier Chen Ridong
2025-09-17  6:04 ` [PATCH -next 02/11] cpuset: remove unused assignment to trialcs->partition_root_state Chen Ridong
2025-09-17  6:04 ` [PATCH -next 03/11] cpuset: change return type of is_partition_[in]valid to bool Chen Ridong
2025-09-17  6:04 ` [PATCH -next 04/11] cpuset: Refactor exclusive CPU mask computation logic Chen Ridong
2025-09-17  6:04 ` [PATCH -next 05/11] cpuset: refactor CPU mask buffer parsing logic Chen Ridong
2025-09-17  6:04 ` [PATCH -next 06/11] cpuset: introduce cpus_excl_conflict and mems_excl_conflict helpers Chen Ridong
2025-09-17  6:04 ` [PATCH -next 07/11] cpuset: refactor out validate_partition Chen Ridong
2025-09-17  6:04 ` [PATCH -next 08/11] cpuset: refactor cpus_allowed_validate_change Chen Ridong
2025-09-19  9:49   ` [PATCH cgroup/for-next] cpuset: fix missing error return in update_cpumask Chen Ridong
2025-09-19 10:12     ` Chen Ridong
2025-09-19 16:43     ` Tejun Heo
2025-09-20  0:54       ` Chen Ridong
2025-09-17  6:04 ` [PATCH -next 09/11] cpuset: introduce partition_cpus_change Chen Ridong
2025-09-17  6:04 ` [PATCH -next 10/11] cpuset: use parse_cpulist for setting cpus.exclusive Chen Ridong
2025-09-17  6:04 ` [PATCH -next 11/11] cpuset: use partition_cpus_change for setting exclusive cpus Chen Ridong
2025-09-17 20:15 ` Tejun Heo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aMsW2WGWrZUm5Qee@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=chenridong@huawei.com \
    --cc=chenridong@huaweicloud.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=lujialin4@huawei.com \
    --cc=mkoutny@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®