From: Arjan van de Ven <arjan@infradead.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@suse.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: [PATCH 2/8] introduce the device async action mechanism
Date: Wed, 15 Jul 2009 06:00:06 -0700 [thread overview]
Message-ID: <20090715060006.71c2e2b6@infradead.org> (raw)
In-Reply-To: <1247643516.26272.77.camel@rzhang-dt>
On Wed, 15 Jul 2009 15:38:36 +0800
Zhang Rui <rui.zhang@intel.com> wrote:
> Introduce the device async action mechanism.
>
> In order to speed up Linux suspend/resume/shutdown process,
> we introduce the device async action mechanism that allow devices
> to suspend/resume/shutdown asynchronously.
>
> The basic idea is that,
> if the suspend/resume/shutdown process of a device set,
> including a root device and its child devices, are independent of
> other devices, we create an async domain for this device set,
> and make them suspend/resume/shutdown asynchronously.
Hi,
I have some concerns about having an async domain per device(group)
rather than having one async domain for all of this, I would
strongly suggest going to one global domain, so that it becomes
more practical to just wait for all async actions like this...
which you need to do during suspend for sure.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-07-15 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 7:38 [PATCH 2/8] introduce the device async action mechanism Zhang Rui
2009-07-15 0:31 ` [linux-pm] " Pavel Machek
2009-07-15 13:00 ` Arjan van de Ven [this message]
2009-07-16 2:05 ` Zhang Rui
2009-07-17 1:11 ` Rafael J. Wysocki
2009-07-17 2:44 ` Zhang Rui
2009-07-19 22:16 ` Pavel Machek
2009-07-20 3:09 ` Zhang Rui
2009-07-20 16:24 ` Rafael J. Wysocki
2009-07-17 4:31 ` Arjan van de Ven
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=20090715060006.71c2e2b6@infradead.org \
--to=arjan@infradead.org \
--cc=arjan.van.de.ven@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=rui.zhang@intel.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