From: Greg KH <gregkh@linuxfoundation.org>
To: Kaiyen Chang <kaiyen.chang@intel.com>
Cc: rafael@kernel.org, pavel@ucw.cz, len.brown@intel.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] PM: Start asynchronous suspend threads upfront
Date: Tue, 18 Jun 2024 13:00:25 +0200 [thread overview]
Message-ID: <2024061801-epilogue-hacker-0494@gregkh> (raw)
In-Reply-To: <20240618093507.2143-2-kaiyen.chang@intel.com>
On Tue, Jun 18, 2024 at 05:35:07PM +0800, Kaiyen Chang wrote:
> Currently, when performing a suspend operation, all devices on the
> dpm_list must wait for preceding "synchronous" devices to complete
> before the main suspend thread can start their suspend routines,
> even if they are "asynchronous". If the suspend routine of a
> synchronous device must enter a waiting state for some reason, it
> will cause the main suspend thread to wait as well, thereby
> delaying the processing of all subsequent devices, including
> asynchronous ones, thus ultimately extending the overall device
> suspend time.
>
> By starting the asynchronous suspend threads of asynchronous
> devices upfront we effectively move those devices towards the
> beginning of dpm_list, without breaking their ordering with respect
> to their parents and children. As a result, even if the main
> suspend thread enters a waiting state, these asynchronous threads
> can continue to run without delay.
>
> Signed-off-by: Kaiyen Chang <kaiyen.chang@intel.com>
> ---
> drivers/base/power/main.c | 90 +++++++++++++++++++++++++--------------
> 1 file changed, 57 insertions(+), 33 deletions(-)
Sorry, but please follow the Intel-documented rules for how to submit
kernel patches before sending them out to the community.
thanks,
greg k-h
next prev parent reply other threads:[~2024-06-18 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 9:35 [PATCH 0/1] PM: Start asynchronous suspend threads upfront Kaiyen Chang
2024-06-18 9:35 ` [PATCH 1/1] " Kaiyen Chang
2024-06-18 11:00 ` Greg KH [this message]
2024-06-18 10:59 ` [PATCH 0/1] " Greg KH
2024-06-19 9:29 ` Chang, Kaiyen
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=2024061801-epilogue-hacker-0494@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kaiyen.chang@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 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.