All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Dirk Behme <dirk.behme@gmail.com>,
	Linux Embedded <linux-embedded@vger.kernel.org>
Subject: Re: Boot time: Initial main memory initialization optimizations?
Date: Mon, 05 May 2014 20:51:28 -0500	[thread overview]
Message-ID: <53684020.5060204@landley.net> (raw)
In-Reply-To: <5367B108.8080206@gmail.com>

On 05/05/14 10:40, Dirk Behme wrote:
> Hi,
> 
> regarding boot time optimization, on an embedded ARM Cortex-A9 based
> system with 512MB or 1GB main memory, we found that initializing this
> main memory takes a somehow large amount of time.
> 
> Initializing 512MB takes <= ~100ms, the additional 512MB on the 1GB take
> <= ~100ms additionally, too. So in sum <= ~200ms for 1GB.
> 
> Having a short look to this, it looks like most of the time is spent in
> arch/arm/mm/init.c in bootmem_init()/arm_bootmem_init()/arm_bootmem_free().
> 
> Has anybody already looked into this if there are any optimizations
> possible? Maybe even some hacks, if the main memory size (512MB/1GB) is
> always known? Any pointers?

There were a couple of longish threads last year. Random links into the
middle of 'em:

http://www.spinics.net/lists/linux-mm/msg54027.html
http://lkml.iu.edu//hypermail/linux/kernel/1306.3/01915.html

> I'm looking for reducing (a) the overall init time and maybe (b) the
> dependency on the memory size.

Basically they were deferring init by abusing the hotplug mechanism, so
the system started with less memory and a background thread added more
of it.

Rob

      reply	other threads:[~2014-05-06  1:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 15:40 Boot time: Initial main memory initialization optimizations? Dirk Behme
2014-05-06  1:51 ` Rob Landley [this message]

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=53684020.5060204@landley.net \
    --to=rob@landley.net \
    --cc=dirk.behme@gmail.com \
    --cc=linux-embedded@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 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.