From: Zhang Rui <rui.zhang@intel.com>
To: Pavel Machek <pavel@ucw.cz>
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>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH 0/8] device async action mechanism
Date: Fri, 17 Jul 2009 09:40:13 +0800 [thread overview]
Message-ID: <1247794814.26272.216.camel@rzhang-dt> (raw)
In-Reply-To: <20090715002916.GC2360@ucw.cz>
On Wed, 2009-07-15 at 08:29 +0800, Pavel Machek wrote:
> Hi!
>
> I notice you are still ccing my @suse.cz address. That one no longer
> works :-(.
>
> > this is the patch set I made to speed up the device
> > suspend/resume/shutdown process.
> >
> > A new mechanism called Device Async Actions is introduced in this patch set.
> > The basic idea is that,
> > 1. device declares to support certain kinds of device async action,
> > like suspend, resume, shutdown, etc.
> > 2. a async domain is create for this device
> > 3. the child device inherits the async domain
> > 4. devices in the same domain suspend/resume/shutdown asynchronously with
> > the other devices.
> >
> > Currently, in order to make sure that it won't bring any side effects,
> > I only convert the ACPI battery and i8042 to use this framework, which reduces
> > 0.5s+ S3 time(suspend time plus resume time)???, from 7.0s to less than 6.5s.
> > and about 0.5s shutdown time in my test.
>
> Hmm, 7seconds is still quite long. What hw is that?
>
7 seconds including both kernel suspend and resume time.
it takes about 3.2s to suspend and 3.8 seconds to resume.
thanks,
rui
next prev parent reply other threads:[~2009-07-17 1:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 7:38 Zhang Rui
2009-07-15 0:29 ` Pavel Machek
2009-07-17 1:40 ` Zhang Rui [this message]
2009-07-15 10:41 ` Andi Kleen
2009-07-16 2:14 ` Zhang Rui
2009-07-16 8:07 ` Andi Kleen
2009-07-16 8:30 ` Zhang Rui
2009-07-16 11:40 ` Henrique de Moraes Holschuh
2009-07-16 13:45 ` Arjan van de Ven
2009-07-16 14:36 ` Fabio Comolli
2009-07-17 1:37 ` Zhang Rui
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=1247794814.26272.216.camel@rzhang-dt \
--to=rui.zhang@intel.com \
--cc=arjan@linux.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@ucw.cz \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®