From: Arjan van de Ven <arjan@linux.intel.com>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-embedded@vger.kernel.org, Greg KH <gregkh@suse.de>,
Martin Mueller <martin@pfump.org>
Subject: Re: Boot time: Kernel start parallelization issue?
Date: Sat, 15 Jan 2011 07:41:40 -0800 [thread overview]
Message-ID: <4D31C034.8040105@linux.intel.com> (raw)
In-Reply-To: <4D315D86.40401@googlemail.com>
On 1/15/2011 12:40 AM, Dirk Behme wrote:
>
> 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?
those patches are obsoleted by the merged async_schedule() calls.
what kernel are you seeing issues on?
if it's something ancient, you should update first.
next prev parent reply other threads:[~2011-01-15 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 8:40 Boot time: Kernel start parallelization issue? Dirk Behme
2011-01-15 15:41 ` Arjan van de Ven [this message]
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=4D31C034.8040105@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=dirk.behme@googlemail.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.