linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	David Hildenbrand <david@redhat.com>
Cc: linux-mm@kvack.org, Arjan van de Ven <arjan@linux.intel.com>,
	Feng Tang <feng.tang@intel.com>
Subject: Re: Deferred Memory Init: How to bring rest of memory online after limiting it with `mem=XG`?
Date: Fri, 04 Dec 2020 14:50:29 -0500	[thread overview]
Message-ID: <87r1o5s64a.fsf@oracle.com> (raw)
In-Reply-To: <75c699e1-0f2f-dd83-5f1f-ebc0753ad762@molgen.mpg.de>

Paul Menzel <pmenzel@molgen.mpg.de> writes:
> If you have ideas how to reduce the boot time of the full 32 GB, that’d 
> be great.

The kernel source has scripts/show_delta to see the relative times
between lines of dmesg.  That combined with the initcall_debug arg
you're already using should go some way toward helping you find where
the boot is slow.

Then there are a variety of tools you can use to drill down further if
necessary, with the simplest being some extra printk's in the kernel
paths that the output points you to if you're willing to do that.

You might also do some more runs to see if your numbers are stable.

thanks,
Daniel


  reply	other threads:[~2020-12-04 19:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 10:51 Deferred Memory Init: How to bring rest of memory online after limiting it with `mem=XG`? Paul Menzel
2020-12-03 12:25 ` David Hildenbrand
2020-12-03 12:52   ` Paul Menzel
2020-12-03 13:06     ` David Hildenbrand
2020-12-03 20:58       ` Daniel Jordan
2020-12-04  7:31         ` Paul Menzel
2020-12-04 19:50           ` Daniel Jordan [this message]
2020-12-04  1:17   ` Feng Tang
2020-12-04  8:05 ` Feng Tang

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=87r1o5s64a.fsf@oracle.com \
    --to=daniel.m.jordan@oracle.com \
    --cc=arjan@linux.intel.com \
    --cc=david@redhat.com \
    --cc=feng.tang@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=pmenzel@molgen.mpg.de \
    /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).