From: Haifeng Xu <haifeng.xu@shopee.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: tj@kernel.org, lizefan.x@bytedance.com, hannes@cmpxchg.org,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup: Simplify code in css_set_move_task
Date: Fri, 28 Oct 2022 19:29:57 +0800 [thread overview]
Message-ID: <adb7418c-39a2-6202-970a-a039ad8201dd@shopee.com> (raw)
In-Reply-To: <20221027080558.GA23269@blackbody.suse.cz>
On 2022/10/27 16:05, Michal Koutný wrote:
> Hello.
>
> On Thu, Oct 20, 2022 at 07:47:01AM +0000, "haifeng.xu" <haifeng.xu@shopee.com> wrote:
>> - lockdep_assert_held(&css_set_lock);
>> + if (!cset || cset is either getting the first task or losing the last(cset))
>> + return;
>
> 1) the guard should be css_set_populated() ^ populated (when unsetting
> the populated trait)
>
> 2) I'd keep the lockdep_assert_held() after it anyway.
>
> Also the commit message should explain what's the reason to move
> css_set_populated() after css_set_move_task().
>
>
> Thanks,
> Michal
Hi, Michal.
1) If calls 'css_set_update_populated' , the cset is either getting the
first task or losing the last. There is a need to update the populated
state of the cset only when 'css_set_populated' returns false.
In other words, the last has been deleted from from_cset and the first
hasn't been added to to_cset yet.
2) Thanks for your suggestion. I'll keep 'lockdep_assert_held'.
3) In order to update the populated state of to_cset the same way
from_cset does, 'css_set_update_populated' is also invoked during the
process of moving a task to to_cset.
Thanks,
Haifeng
next prev parent reply other threads:[~2022-10-28 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 7:47 haifeng.xu
2022-10-27 8:05 ` Michal Koutný
2022-10-28 11:29 ` Haifeng Xu [this message]
2022-10-31 13:11 ` Michal Koutný
2022-11-03 2:13 ` Haifeng Xu
2022-11-03 2:31 ` Tejun Heo
2022-11-03 14:55 ` Haifeng Xu
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=adb7418c-39a2-6202-970a-a039ad8201dd@shopee.com \
--to=haifeng.xu@shopee.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mkoutny@suse.com \
--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
all inboxes | Powered by JetHome®