public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: chenridong <chenridong@huawei.com>
To: Kamalesh Babulal <kamalesh.babulal@oracle.com>, <tj@kernel.org>,
	<lizefan.x@bytedance.com>, <hannes@cmpxchg.org>,
	<longman@redhat.com>, <adityakali@google.com>,
	<sergeh@kernel.org>, <mkoutny@suse.com>
Cc: <cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] cgroup/cpuset: add dec_attach_in_progress helper
Date: Thu, 25 Jul 2024 19:40:15 +0800	[thread overview]
Message-ID: <de6958aa-27f8-4baa-b76d-88266d009f81@huawei.com> (raw)
In-Reply-To: <e5c92f54-d767-4e71-9f57-9352923bd3e7@oracle.com>



On 2024/7/25 19:01, Kamalesh Babulal wrote:
> 
> 
> On 7/25/24 7:25 AM, Chen Ridong wrote:
>> There are several functions to decrease attach_in_progress, and they
>> will wake up cpuset_attach_wq when attach_in_progress is zero. So,
>> add a helper to make it concise.
>>
>> Signed-off-by: Chen Ridong <chenridong@huawei.com>
>> ---
>>   kernel/cgroup/cpuset.c | 28 +++++++++++++++-------------
>>   1 file changed, 15 insertions(+), 13 deletions(-)
>>
>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
>> index d4322619e59a..c241845694ac 100644
>> --- a/kernel/cgroup/cpuset.c
>> +++ b/kernel/cgroup/cpuset.c
>> @@ -490,6 +490,17 @@ static inline void check_insane_mems_config(nodemask_t *nodes)
>>   	}
>>   }
>>   
>> +/*
>> + * decrease cs->attach_in_progress.
>> + * wake_up cpuset_attach_wq if cs->attach_in_progress==0.
> 
> In the description, adding locking constraint of cpuset_mutex would be helpful.
> Something like "cpuset_mutex must be held by the caller."
> 
Thank you, I will to that.
>> + */
>> +static inline void dec_attach_in_progress(struct cpuset *cs)
>> +{
>> +	cs->attach_in_progress--;
>> +	if (!cs->attach_in_progress)
>> +		wake_up(&cpuset_attach_wq);
>> +}
>> +
>>   /*
>>    * Cgroup v2 behavior is used on the "cpus" and "mems" control files when
>>    * on default hierarchy or when the cpuset_v2_mode flag is set by mounting
>> @@ -3421,9 +3432,7 @@ static void cpuset_cancel_attach(struct cgroup_taskset *tset)
>>   	cs = css_cs(css);
>>   
>>   	mutex_lock(&cpuset_mutex);
>> -	cs->attach_in_progress--;
>> -	if (!cs->attach_in_progress)
>> -		wake_up(&cpuset_attach_wq);
>> +	dec_attach_in_progress(cs);
>>   
>>   	if (cs->nr_migrate_dl_tasks) {
>>   		int cpu = cpumask_any(cs->effective_cpus);
>> @@ -3538,9 +3547,7 @@ static void cpuset_attach(struct cgroup_taskset *tset)
>>   		reset_migrate_dl_data(cs);
>>   	}
>>   
>> -	cs->attach_in_progress--;
>> -	if (!cs->attach_in_progress)
>> -		wake_up(&cpuset_attach_wq);
>> +	dec_attach_in_progress(cs);
>>   
>>   	mutex_unlock(&cpuset_mutex);
>>   }
>> @@ -4284,9 +4291,7 @@ static void cpuset_cancel_fork(struct task_struct *task, struct css_set *cset)
>>   		return;
>>   
>>   	mutex_lock(&cpuset_mutex);
>> -	cs->attach_in_progress--;
>> -	if (!cs->attach_in_progress)
>> -		wake_up(&cpuset_attach_wq);
>> +	dec_attach_in_progress(cs);
>>   	mutex_unlock(&cpuset_mutex);
>>   }
>>   
>> @@ -4319,10 +4324,7 @@ static void cpuset_fork(struct task_struct *task)
>>   	guarantee_online_mems(cs, &cpuset_attach_nodemask_to);
>>   	cpuset_attach_task(cs, task);
>>   
>> -	cs->attach_in_progress--;
>> -	if (!cs->attach_in_progress)
>> -		wake_up(&cpuset_attach_wq);
>> -
>> +	dec_attach_in_progress(cs);
>>   	mutex_unlock(&cpuset_mutex);
>>   }
>>   
> 

  reply	other threads:[~2024-07-25 11:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  1:55 [PATCH -next] cgroup/cpuset: add dec_attach_in_progress helper Chen Ridong
2024-07-25 11:01 ` Kamalesh Babulal
2024-07-25 11:40   ` chenridong [this message]
2024-07-25 19:07     ` Waiman Long
2024-07-26  1:00       ` chenridong

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=de6958aa-27f8-4baa-b76d-88266d009f81@huawei.com \
    --to=chenridong@huawei.com \
    --cc=adityakali@google.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kamalesh.babulal@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=sergeh@kernel.org \
    --cc=tj@kernel.org \
    /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