Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758527AbYHTPYZ (ORCPT ); Wed, 20 Aug 2008 11:24:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752882AbYHTPYQ (ORCPT ); Wed, 20 Aug 2008 11:24:16 -0400 Received: from gateway-1237.mvista.com ([63.81.120.158]:38485 "EHLO gateway-1237.mvista.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752770AbYHTPYP (ORCPT ); Wed, 20 Aug 2008 11:24:15 -0400 Subject: Re: slower initcalls in -next From: Daniel Walker To: Takashi Iwai Cc: Arjan van de Ven , lkml In-Reply-To: References: <1219179084.18104.11.camel@dhcp32.mvista.com> Content-Type: text/plain Date: Wed, 20 Aug 2008 08:24:11 -0700 Message-Id: <1219245851.18104.24.camel@dhcp32.mvista.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 900 Lines: 21 On Wed, 2008-08-20 at 09:58 +0200, Takashi Iwai wrote: > At least, all alsa_* calls are only for ISA devices, and I don't think > it's worth to optimize. Changing such hardcoded delays could break > the running system easily. > > However, some of the above are definitely interesting to investigate > as they are mostly built-in and affect almost all people. I didn't realize it till later , but the list is a little misleading .. Those times are a mix of execution, and blocking.. I think the top one (49 seconds!) was blocked most of the time, since ub_init() doesn't look very complex. I'm not sure if it what it was blocked on, or why .. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/