All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: linux-embedded@vger.kernel.org
Cc: Arjan van de Ven <arjan@linux.intel.com>,
	Greg KH <gregkh@suse.de>, Martin Mueller <martin@pfump.org>
Subject: Boot time: Kernel start parallelization issue?
Date: Sat, 15 Jan 2011 09:40:38 +0100	[thread overview]
Message-ID: <4D315D86.40401@googlemail.com> (raw)


There are some reports [1] [2] looking at the boot time of embedded 
(ARM?) systems using initcall debug [3]. Both reports seem to show 
that they have issues with the start up sequence of the kernel being 
completely single-threaded. In [2] Greg mentions that on a x86 box 
multi-threads are happening and that there he doesn't see this issue. 
On the other hand, both reports mention Arjan's async initcall patches 
[4] to help against the issue. I.e. introducing some parallelization 
(on ARM) does help, too.

With this, I wonder

- if anybody faces similar issues with single-threaded only kernel 
start on embedded (ARM?) systems? Or if this is known? Or if there are 
fixes for this?

- if we somehow should try to 're-activate' Arjan's async initcall 
patches?

Any ideas?

Many thanks and best regards

Dirk

P.S.: I couldn't find a mail address of Alex Gonzalez, the author of 
[1], to put him into CC. If anybody knows him, please feel free to add 
him to this thread. Thanks!

[1] 
http://www.lindusembedded.com/blog/2010/06/02/measuring-the-boot-time-of-an-embedded-linux-device/

[2] http://thread.gmane.org/gmane.linux.usb.general/41181 (mainly the 
last mail of this thread: 
http://article.gmane.org/gmane.linux.usb.general/41619)

[3] http://www.elinux.org/Initcall_Debug

[4] http://lwn.net/Articles/299591/

             reply	other threads:[~2011-01-15  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15  8:40 Dirk Behme [this message]
2011-01-15 15:41 ` Boot time: Kernel start parallelization issue? Arjan van de Ven
2011-01-15 16:18   ` Dirk Behme
2011-01-16  7:33     ` Dirk Behme
2011-01-17  0:13       ` Arjan van de Ven

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=4D315D86.40401@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --cc=arjan@linux.intel.com \
    --cc=gregkh@suse.de \
    --cc=linux-embedded@vger.kernel.org \
    --cc=martin@pfump.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.