From: Arjan van de Ven <arjan@linux.intel.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Zhang Rui <rui.zhang@intel.com>, Andi Kleen <andi@firstfloor.org>,
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>
Subject: Re: [PATCH 0/8] device async action mechanism
Date: Thu, 16 Jul 2009 06:45:16 -0700 [thread overview]
Message-ID: <4A5F2EEC.8010508@linux.intel.com> (raw)
In-Reply-To: <20090716114020.GA11928@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
> On Thu, 16 Jul 2009, Zhang Rui wrote:
>> the kernel device suspend time is reduced from 3.2s to 2.8s after
>> applying this patch set in my test box.
>
> It will give even a bigger boot time saving on ThinkPads, where there is a
> Synaptics (or ALPS if you are unlucky) touchpad with the trackpoint behind
> it... it takes about 2s to init both devices here. That's two seconds of
> boot time you can shove off if it is being initialized assyncronously :-)
>
that's a different problem that I don't think this will solve; as long
as you keep the boot of the kernel wait for all async actions, you're going
to hit that wait. In Moblin we have a (bad) patch to not do the wait,
at some point we need to figure how to get a mainline-able patch....
next prev parent reply other threads:[~2009-07-16 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 7:38 [PATCH 0/8] device async action mechanism Zhang Rui
2009-07-15 0:29 ` Pavel Machek
2009-07-17 1:40 ` Zhang Rui
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 [this message]
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=4A5F2EEC.8010508@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--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