From: Waiman Long <waiman.long@hp.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mel Gorman <mgorman@suse.de>, Linux-MM <linux-mm@kvack.org>,
Nathan Zimmer <nzimmer@sgi.com>, Daniel Rahn <drahn@suse.com>,
Davidlohr Bueso <dbueso@suse.com>,
Dave Hansen <dave.hansen@intel.com>, Tom Vaden <tom.vaden@hp.com>,
Scott Norton <scott.norton@hp.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/14] Parallel memory initialisation
Date: Wed, 15 Apr 2015 12:18:58 -0400 [thread overview]
Message-ID: <552E8F72.408@hp.com> (raw)
In-Reply-To: <20150415144818.GX5029@twins.programming.kicks-ass.net>
On 04/15/2015 10:48 AM, Peter Zijlstra wrote:
> On Wed, Apr 15, 2015 at 03:34:20PM +0100, Mel Gorman wrote:
>> On Wed, Apr 15, 2015 at 04:27:31PM +0200, Peter Zijlstra wrote:
>>> On Wed, Apr 15, 2015 at 09:15:50AM -0400, Waiman Long wrote:
>>>> I had included your patch with the 4.0 kernel and booted up a 16-socket
>>>> 12-TB machine. I measured the elapsed time from the elilo prompt to the
>>>> availability of ssh login. Without the patch, the bootup time was 404s. It
>>>> was reduced to 298s with the patch. So there was about 100s reduction in
>>>> bootup time (1/4 of the total).
>>> But you cheat! :-)
>>>
>>> How long between power on and the elilo prompt? Do the 100 seconds
>>> matter on that time scale?
>> Calling it cheating is a *bit* harsh as the POST times vary considerably
>> between manufacturers. While I'm interested in Waiman's answer, I'm told
>> that those that really care about minimising reboot times will use kexec
>> to avoid POST. The 100 seconds is 100 seconds, whether that is 25% in
>> all cases is a different matter.
> Sure POST times vary, but its consistently stupid long :-) I'm forever
> thinking my EX machine died because its not coming back from a power
> cycle, and mine isn't really _that_ large.
I agree with that. I always complain about the long POST time of those
server machines.
As for Mel's patch, what I wanted to show is its impact on the OS bootup
part of the boot process. We have no control on how long the firmware
POST is, so there is no point in lumping them into the discussion.
Cheers,
Longman
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-04-15 16:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 10:16 [RFC PATCH 0/14] Parallel memory initialisation Mel Gorman
2015-04-13 10:16 ` [PATCH 01/14] memblock: Introduce a for_each_reserved_mem_region iterator Mel Gorman
2015-04-13 10:16 ` [PATCH 02/14] mm: meminit: Move page initialization into a separate function Mel Gorman
2015-04-13 10:16 ` [PATCH 03/14] mm: meminit: Only set page reserved in the memblock region Mel Gorman
2015-04-13 10:16 ` [PATCH 04/14] mm: page_alloc: Pass PFN to __free_pages_bootmem Mel Gorman
2015-04-13 10:16 ` [PATCH 05/14] mm: meminit: Make __early_pfn_to_nid SMP-safe and introduce meminit_pfn_in_nid Mel Gorman
2015-04-13 10:16 ` [PATCH 06/14] mm: meminit: Inline some helper functions Mel Gorman
2015-04-13 10:16 ` [PATCH 07/14] mm: meminit: Partially initialise memory if CONFIG_DEFERRED_MEM_INIT is set Mel Gorman
2015-04-13 10:17 ` [PATCH 08/14] mm: meminit: Initialise remaining memory in parallel with kswapd Mel Gorman
2015-04-13 10:17 ` [PATCH 09/14] mm: meminit: Minimise number of pfn->page lookups during initialisation Mel Gorman
2015-04-13 10:17 ` [PATCH 10/14] x86: mm: Enable deferred memory initialisation on x86-64 Mel Gorman
2015-04-13 18:21 ` Paul Bolle
2015-04-13 10:17 ` [PATCH 11/14] mm: meminit: Control parallel memory initialisation from command line and config Mel Gorman
2015-04-13 10:17 ` [PATCH 12/14] mm: meminit: Free pages in large chunks where possible Mel Gorman
2015-04-13 10:17 ` [PATCH 13/14] mm: meminit: Reduce number of times pageblocks are set during initialisation Mel Gorman
2015-04-13 10:17 ` [PATCH 14/14] mm: meminit: Remove mminit_verify_page_links Mel Gorman
2015-04-13 10:29 ` [RFC PATCH 0/14] Parallel memory initialisation Mel Gorman
2015-04-15 13:15 ` Waiman Long
2015-04-15 13:38 ` Mel Gorman
2015-04-15 14:50 ` Waiman Long
2015-04-15 15:44 ` Mel Gorman
2015-04-15 21:37 ` nzimmer
2015-04-16 18:20 ` Waiman Long
2015-04-15 14:27 ` Peter Zijlstra
2015-04-15 14:34 ` Mel Gorman
2015-04-15 14:48 ` Peter Zijlstra
2015-04-15 16:18 ` Waiman Long [this message]
2015-04-15 16:42 ` Norton, Scott J
2015-04-16 7:25 ` Andrew Morton
2015-04-16 8:46 ` Mel Gorman
2015-04-16 17:26 ` Andrew Morton
2015-04-16 17:37 ` Mel Gorman
-- strict thread matches above, loose matches on Subject: below --
2015-04-16 7:51 Daniel J Blueman
2015-04-20 3:15 ` Daniel J Blueman
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=552E8F72.408@hp.com \
--to=waiman.long@hp.com \
--cc=dave.hansen@intel.com \
--cc=dbueso@suse.com \
--cc=drahn@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=nzimmer@sgi.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.com \
--cc=tom.vaden@hp.com \
/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).