From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [PATCH 0/8] device async action mechanism Date: Thu, 16 Jul 2009 06:45:16 -0700 Message-ID: <4A5F2EEC.8010508@linux.intel.com> References: <1247643512.26272.74.camel@rzhang-dt> <87ocrm6xeq.fsf@basil.nowhere.org> <1247710483.26272.170.camel@rzhang-dt> <20090716114020.GA11928@khazad-dum.debian.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mga12.intel.com ([143.182.124.36]:5853 "EHLO azsmga102.ch.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756680AbZGPNpU (ORCPT ); Thu, 16 Jul 2009 09:45:20 -0400 In-Reply-To: <20090716114020.GA11928@khazad-dum.debian.net> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Henrique de Moraes Holschuh Cc: Zhang Rui , Andi Kleen , Linux Kernel Mailing List , linux-pm , linux-acpi , Len Brown 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....