linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lhns-devel] Re: Who's doing what with cpu/memory/node hotplug?
Date: Tue, 18 May 2004 20:16:30 +0000	[thread overview]
Message-ID: <20040518131630.A28921@unix-os.sc.intel.com> (raw)
In-Reply-To: <20040513150842.22F5.YGOTO@us.fujitsu.com>

On Tue, May 18, 2004 at 09:58:38AM -0500, Russ Anderson wrote:
> Matthias Fouquet-Lapar wrote:
> > 
> > [ Just as a site-note, I always wondered if hotplug would be a useful feature
> >   for larger configurations to reduce boot-time. For example, on a 64P system 
> >   you start the kernel on some "root" CPU with a relativly small amount of
> >   memory, so it should boot relativly fast. While the system is going into
> >   the desired run-level, hotplug/add now adds in parallel all available CPUs,
> >   main memory, I/O etc. The idea is that you probably don't need 64P and
> >   1 Terabyte to start system services
> > ]
> 
> I can certainly think of cases (customers) where minimizing the total
> system down time is a huge issue.  Getting a subset of the system
> back into production as quickly as possible would be very desirable.
> 
> Another advantage of that type boot process is that it would catch
> any bugs (or regressions) in the hot add code.  At a minumum, it 
> would be a very good test of the hot add functionality.
> 
> I think a boot option to allow that type of booting process
> would be a good idea.

The boot already follows the same methodology, the boot cpu comes up, and the rest of the cpu's are brought up. for e.g. smp_init() does call cpu_up() which is the same path for hotplug.

Not sure if cpu_up is a time consuming process, i think if you have more cpu's
the startup could be faster as you have now more resources to complete the 
statup of kernel.

Often what i have seen is that the IO part of the probe is the most time
consuming process. Splitting the discovery of controllers and boot resources
first, and then deferring the rest if the io discovery process would 
speedup boot. Also its your firmware that would do the same work as OS 
in identifying all the controllers and disks upfront that contributes to 
slow boot.

bringup all cpu() and then defer part of the probe/discovery (especially
disks) in parallel would provide real benefit i think.

Cheers,
ashok


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-05-18 20:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14  0:13 [Lhns-devel] Re: Who's doing what with cpu/memory/node hotplug? Yasunori Goto
2004-05-14  1:06 ` Paul Jackson
2004-05-14  1:28 ` Dave Hansen
2004-05-14  2:09 ` Jesse Barnes
2004-05-14  3:02 ` Keiichiro Tokunaga
2004-05-14  3:21 ` Dave Hansen
2004-05-17  2:34 ` Kenji Kaneshige
2004-05-17  5:31 ` Dave Hansen
2004-05-17  7:35 ` Matthias Fouquet-Lapar
2004-05-17  8:23 ` Dave Hansen
2004-05-17  8:38 ` Matthias Fouquet-Lapar
2004-05-17 15:45 ` Grant Grundler
2004-05-17 15:52 ` Dave Hansen
2004-05-17 16:00 ` Ashok Raj
2004-05-17 19:15 ` Matthias Fouquet-Lapar
2004-05-17 23:01 ` Matthew Dobson
2004-05-17 23:18 ` Luck, Tony
2004-05-17 23:28 ` Dave Hansen
2004-05-17 23:36 ` Jesse Barnes
2004-05-17 23:54 ` Grant Grundler
2004-05-18 14:58 ` Russ Anderson
2004-05-18 20:16 ` Ashok Raj [this message]
2004-05-18 21:01 ` Jack Steiner
2004-05-18 21:05 ` Andi Kleen
2004-05-18 21:12 ` Greg KH
2004-05-19  5:25 ` Matthias Fouquet-Lapar
2004-05-19  9:17 ` Paul Jackson
2004-05-19  9:30 ` Matthias Fouquet-Lapar
2004-05-19 10:22 ` Paul Jackson
2004-05-19 14:40 ` Howell, David P
2004-05-19 14:56 ` Matthias Fouquet-Lapar

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=20040518131630.A28921@unix-os.sc.intel.com \
    --to=ashok.raj@intel.com \
    --cc=linux-ia64@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).