From: Peter Zijlstra <peterz@infradead.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: rjw@rjwysocki.net, mingo@kernel.org, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com, rostedt@goodmis.org, mgorman@suse.de,
Will Deacon <will@kernel.org>, Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] freezer,sched: Rewrite core freezer logic
Date: Tue, 15 Jun 2021 23:35:18 +0200 [thread overview]
Message-ID: <20210615213518.GC4272@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20210615154539.GA30333@redhat.com>
On Tue, Jun 15, 2021 at 05:45:39PM +0200, Oleg Nesterov wrote:
> But this reminds me... can't we implement selective wakeups? So that if a
> task T sleeps in state = STOPPED | FROZEN, then ttwu(T, FROZEN) won't wake
> it up, it will only clear FROZEN from T->state. Similarly, ttwu(T, STOPPED)
> will leave this task with state == FROZEN.
All this started because I didn't want to touch the wakeup path for
freezing :/
> See also
>
> https://lore.kernel.org/lkml/20131112162136.GA29065@redhat.com/
> https://lore.kernel.org/lkml/20131113170724.GA17739@redhat.com/
>
> just to remind you that we already discussed TASK_FROZEN a little bit almost
> 10 years ago ;)
>
> What has been shall be, and what has been done is what will be done, and
> there is nothing new under the sun.
Ha!, I had completely forgotten.
next prev parent reply other threads:[~2021-06-15 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 8:45 [PATCH] freezer,sched: Rewrite core freezer logic Peter Zijlstra
2021-06-11 8:46 ` Peter Zijlstra
2021-06-11 13:58 ` Rafael J. Wysocki
2021-06-14 15:42 ` Oleg Nesterov
2021-06-14 16:12 ` Peter Zijlstra
2021-06-14 16:54 ` Oleg Nesterov
2021-06-14 18:38 ` Peter Zijlstra
2021-06-15 15:45 ` Oleg Nesterov
2021-06-15 21:35 ` Peter Zijlstra [this message]
2021-06-15 21:50 ` Peter Zijlstra
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=20210615213518.GC4272@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=will@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 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.