From: Peter Zijlstra <peterz@infradead.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Zihuan Zhang <zhangzihuan@kylinos.cn>,
pavel@kernel.org, len.brown@intel.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v3 1/1] PM / Freezer: Skip zombie/dead processes to
Date: Fri, 4 Jul 2025 10:19:41 +0200 [thread overview]
Message-ID: <20250704081941.GC2001818@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CAJZ5v0j29Nu2nitmj6tPhOQYuSaHBtXQVR21ikDtrxpejPdW8A@mail.gmail.com>
On Thu, Jul 03, 2025 at 07:15:23PM +0200, Rafael J. Wysocki wrote:
> > How realistic is it to have a significant amount of zombies when
> > freezing? This seems like an artificial corner case at best.
> >
> > Zombie tasks are stuck waiting on their parent to consume their exit
> > state or something, right? And those parents being frozen, they pretty
> > much stay there.
> >
> > So I suppose the logic holds, but urgh, do we really need this?
>
> Unlikely in practice, but the code change is small and it would be
> prudent to get this addressed IMV (at least so we don't need to
> revisit it).
>
> But I would ask for a comment above this check to explain that zombies
> need not be frozen.
Depending on where they wait (I can't seem to find in a hurry) it might
make sense to make that wait FREEZABLE anyway.
For example, AFAICT it wouldn't hurt, and might even help some, to make
kernel/exit.c:do_wait() TASK_FREEZABLE.
So where do ZOMBIEs sleep? Don't they simply pass through do_task_dead()
and never get scheduled again? Notably, do_task_dead() already marks the
tasks as PF_NOFREEZE.
Anyway, yes, the condition it adds is relatively simple, but I really
don't see why we should complicate things *at*all*.
next prev parent reply other threads:[~2025-07-04 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 10:12 [PATCH v3 0/1] PM / Freezer: Skip zombie/dead processes to reduce Zihuan Zhang
2025-06-11 10:12 ` [PATCH v3 1/1] PM / Freezer: Skip zombie/dead processes to Zihuan Zhang
2025-07-03 14:15 ` Rafael J. Wysocki
2025-07-03 16:40 ` Peter Zijlstra
2025-07-03 17:15 ` Rafael J. Wysocki
2025-07-04 1:45 ` Zihuan Zhang
2025-07-04 8:19 ` Peter Zijlstra [this message]
2025-07-04 8:48 ` Zihuan Zhang
2025-07-04 9:21 ` Peter Zijlstra
2025-07-07 1:00 ` Zihuan Zhang
2025-07-07 8:42 ` Peter Zijlstra
2025-07-08 0:56 ` Zihuan Zhang
2025-07-16 16:16 ` Oleg Nesterov
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=20250704081941.GC2001818@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=zhangzihuan@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.