From: Takashi Iwai <tiwai@suse.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: slower initcalls in -next
Date: Wed, 20 Aug 2008 09:58:03 +0200 [thread overview]
Message-ID: <s5h63pwnmno.wl%tiwai@suse.de> (raw)
In-Reply-To: <1219179084.18104.11.camel@dhcp32.mvista.com>
At Tue, 19 Aug 2008 13:51:24 -0700,
Daniel Walker wrote:
>
>
> I was testing out todays -next I saw fastboot was included, which got me
> interested so I made a list of the slower initcalls. This was an
> allyesconfig on 32bit x86, which means these numbers are somewhat
> inflated w/ debugging enabled.
> The top 25 below,
>
> initcall ub_init+0x0/0x76 returned 0 after 49465 msecs
> initcall rtrack_init+0x0/0xec returned 0 after 30529 msecs
> initcall net_olddevs_init+0x0/0x129 returned 0 after 25032 msecs
> initcall alsa_card_miro_init+0x0/0x19 returned 0 after 11562 msecs
> initcall cadet_init+0x0/0x156 returned -1 after 3173 msecs
> initcall mousedev_init+0x0/0x7d returned 0 after 2658 msecs
> initcall pty_init+0x0/0x449 returned 0 after 1735 msecs
> initcall tcpprobe_init+0x0/0xc3 returned 0 after 1388 msecs
> initcall sermouse_init+0x0/0x1b returned 0 after 1274 msecs
> initcall microcode_intel_module_init+0x0/0x43 returned 0 after 1247 msecs
> initcall ipx_init+0x0/0xd7 returned 0 after 1014 msecs
> initcall piix_init+0x0/0x29 returned 0 after 747 msecs
> initcall raid5_init+0x0/0x37 returned 0 after 648 msecs
> initcall init_rfd_ftl+0x0/0x14 returned 0 after 579 msecs
> initcall param_sysfs_init+0x0/0x143 returned 0 after 522 msecs
> initcall serial8250_init+0x0/0xef returned 0 after 507 msecs
> initcall init_sc520cdp+0x0/0x1d8 returned -5 after 415 msecs
> initcall isapnp_init+0x0/0xca6 returned 0 after 347 msecs
> initcall pci_init+0x0/0x31 returned 0 after 308 msecs
> initcall tty_init+0x0/0x19c returned 0 after 305 msecs
> initcall ehci_hcd_init+0x0/0x9f returned 0 after 305 msecs
> initcall alsa_card_sb8_init+0x0/0x19 returned -19 after 305 msecs
> initcall uhci_hcd_init+0x0/0xd4 returned 0 after 297 msecs
> initcall com90xx_init+0x0/0xd6f returned -5 after 293 msecs
> initcall alsa_card_wavefront_init+0x0/0x52 returned 0 after 286 msecs
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.
thanks,
Takashi
next prev parent reply other threads:[~2008-08-20 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 20:51 Daniel Walker
2008-08-20 7:58 ` Takashi Iwai [this message]
2008-08-20 15:24 ` Daniel Walker
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=s5h63pwnmno.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=arjan@infradead.org \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
/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®