Linux Power Management development
 help / color / mirror / Atom feed
From: Zihuan Zhang <zhangzihuan@kylinos.cn>
To: Peter Zijlstra <peterz@infradead.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: 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 16:48:20 +0800	[thread overview]
Message-ID: <67997bdd-d00a-413a-a565-188c4b06f385@kylinos.cn> (raw)
In-Reply-To: <20250704081941.GC2001818@noisy.programming.kicks-ass.net>

Hi Peter,

Thanks for the feedback.

在 2025/7/4 16:19, Peter Zijlstra 写道:
>                                
> 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*.

You’re absolutely right — zombie processes won’t be frozen in practice, 
since PF_NOFREEZE is already set in do_task_dead(). However, if we don’t 
explicitly skip them early in try_to_freeze_task(), they still go 
through the freezer logic path, including calls like freeze_task() → 
freezing() before eventually returning without freezing.

This not only introduces unnecessary code path traversal, but also 
involves locking (e.g., spin_lock_irqsave/restore()), which could be 
avoided altogether if we bail out earlier.

Additionally, skipping zombies directly helps reduce the list traversal 
overhead in freeze_processes(), especially on systems with a large 
number of tasks, where zombies can account for a non-trivial fraction.

So while the practical effect might be small, the gain is low-risk and 
helps streamline the freezer logic a bit more.

  reply	other threads:[~2025-07-04  8:48 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
2025-07-04  8:48           ` Zihuan Zhang [this message]
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=67997bdd-d00a-413a-a565-188c4b06f385@kylinos.cn \
    --to=zhangzihuan@kylinos.cn \
    --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=peterz@infradead.org \
    --cc=rafael@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