linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: why does "mem auto-init: clearing system memory may take some time..." takes about 14 sec under 5.4.17 but only few msec under 5.5.1?
Date: Sat, 1 Feb 2020 18:52:26 +0100	[thread overview]
Message-ID: <c7a23250-6b23-2a9e-88c8-924c34fb9139@gmx.de> (raw)

I do wonder (and I'm surprised) about increased boot speed according to dmesg for thi9s hardend Gentoo Linux system:
Linux mr-fox 5.5.1 #1 SMP Sat Feb 1 18:25:21 CET 2020 x86_64 Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz GenuineIntel GNU/Linux

Under 5.4.17 I do have usually 14 sec to wait:

[    0.497171] mem auto-init: stack:byref_all, heap alloc:on, heap free:on
[    0.497171] mem auto-init: clearing system memory may take some time...
[    0.501549] Calgary: detecting Calgary via BIOS EBDA area
[    0.501550] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[   14.083235] Memory: 131812972K/134101088K available (12291K kernel code, 1400K rwdata, 1912K rodata, 1272K init, 2040K bss, 2288116K reserved, 0K cma-reserved)
[   14.083342] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=1
[   14.083350] Kernel/User page tables isolation: enabled
[   14.083403] rcu: Hierarchical RCU implementation.
[   14.083404] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[   14.083414] NR_IRQS: 4352, nr_irqs: 928, preallocated irqs: 16

but with 5.5.1 there's no wait?:

[    0.000000] mem auto-init: stack:byref_all, heap alloc:on, heap free:on
[    0.000000] mem auto-init: clearing system memory may take some time...
[    0.000000] Memory: 131812876K/134101088K available (12291K kernel code, 1412K rwdata, 1936K rodata, 1260K init, 2012K bss, 2288212K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=1
[    0.000000] Kernel/User page tables isolation: enabled
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] NR_IRQS: 4352, nr_irqs: 928, preallocated irqs: 16
[    0.000000] random: get_random_bytes called from start_kernel+0x4a8/0x659 with crng_init=0

Do I miss something? (The kernel config was derived via "make oldconfig").

--
Toralf

             reply	other threads:[~2020-02-01 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 17:52 Toralf Förster [this message]
2020-03-30  2:55 ` why does "mem auto-init: clearing system memory may take some time..." takes about 14 sec under 5.4.17 but only few msec under 5.5.1? Randy Dunlap
2020-03-30  7:12   ` Toralf Förster
2020-03-30  9:12   ` Toralf Förster
2020-04-03  1:33     ` Randy Dunlap

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=c7a23250-6b23-2a9e-88c8-924c34fb9139@gmx.de \
    --to=toralf.foerster@gmx.de \
    --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;
as well as URLs for NNTP newsgroup(s).