From: Tejun Heo <tj@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] cgroup: avoid the unnecessary list_add(dying_tasks) in cgroup_exit()
Date: Wed, 19 Jun 2024 07:33:47 -1000 [thread overview]
Message-ID: <ZnMWe4dcz3M6cyAU@slm.duckdns.org> (raw)
In-Reply-To: <20240617143152.GA10404@redhat.com>
On Mon, Jun 17, 2024 at 04:31:52PM +0200, Oleg Nesterov wrote:
> cgroup_exit() needs to do this only if the exiting task is a leader and it
> is not the last live thread. The patch doesn't use delay_group_leader(),
> atomic_read(signal->live) matches the code css_task_iter_advance() more.
>
> cgroup_release() can now check list_empty(task->cg_list) before it takes
> css_set_lock and calls ss_set_skip_task_iters().
>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Applied to cgroup/for-6.11.
Thanks.
--
tejun
prev parent reply other threads:[~2024-06-19 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 14:31 [PATCH 0/1] cgroup: avoid the unnecessary list_add(dying_tasks) in cgroup_exit() Oleg Nesterov
2024-06-17 14:31 ` [PATCH 1/1] " Oleg Nesterov
2024-06-19 17:33 ` 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=ZnMWe4dcz3M6cyAU@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=oleg@redhat.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