mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Noam Camus <noamca@mellanox.com>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	Chris Metcalf <cmetcalf@mellanox.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"anna-maria@linutronix.de" <anna-maria@linutronix.de>,
	Eitan Rabin <rabin@mellanox.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Reduce Linux boot time on Large scale system
Date: Wed, 19 Apr 2017 09:49:44 +0200	[thread overview]
Message-ID: <20170419074944.lacscblx2ulhfcd3@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <AM4PR05MB1636E0752C76AA42A777F81AAA0B0@AM4PR05MB1636.eurprd05.prod.outlook.com>

On Tue, Apr 04, 2017 at 04:39:06PM +0000, Noam Camus wrote:
> Hi Peter & Vineet
> 
> I wish to reduce boot time of my platform ARC/plat-eznps (4K CPUs).
> My analysis is that most boot time is spent over cpu_up() for all CPUs
> Measurements are about 66mS per CPU and Totally over 4 minutes (I got 800MHz cores).
> 
> I see that smp_init() just iterate over all present cpus one by one.
> I wish to know if there was an attempt to optimize this with some parallel work?
> 
> Are you aware of some method / trick  that will help me to reduce boot time?
> Any suggestion how this can be done?

So attempts have been made in the past but Thomas shot them down for
being gross hacks (they were).

But Thomas has now (mostly) completed rewriting the CPU hotplug
machinery and he has at some point outlined means of achieving what
you're after.

I've added him to Cc so he can correct me where I'm wrong, as I've not
looked into this in much detail after he mucked up all I knew about CPU
hotplug.

Since each CPU is now responsible for its own bootstrap, we can now kick
all the CPUs awake without waiting for them to complete the online
stage.

There might however be code that assumes CPUs come up one at a time, so
you'll need to audit for that. Its not going to be a trivial thing.

       reply	other threads:[~2017-04-19  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM4PR05MB1636E0752C76AA42A777F81AAA0B0@AM4PR05MB1636.eurprd05.prod.outlook.com>
2017-04-19  7:49 ` Peter Zijlstra [this message]
2017-04-19  8:58   ` Thomas Gleixner
2017-04-19 10:08     ` Noam Camus
2017-04-19 10:35       ` Thomas Gleixner

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=20170419074944.lacscblx2ulhfcd3@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=anna-maria@linutronix.de \
    --cc=cmetcalf@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noamca@mellanox.com \
    --cc=rabin@mellanox.com \
    --cc=tglx@linutronix.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

all inboxes | Powered by JetHome®