lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 21 Jun 2013 13:28:11 -0700 From: Yinghai Lu <yinghai@...nel.org> To: Nathan Zimmer <nzimmer@....com> Cc: Greg KH <gregkh@...uxfoundation.org>, "H. Peter Anvin" <hpa@...or.com>, Robin Holt <holt@....com>, Mike Travis <travis@....com>, Rob Landley <rob@...dley.net>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Andrew Morton <akpm@...ux-foundation.org>, "the arch/x86 maintainers" <x86@...nel.org>, linux-doc@...r.kernel.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [RFC 0/2] Delay initializing of large sections of memory On Fri, Jun 21, 2013 at 12:19 PM, Nathan Zimmer <nzimmer@....com> wrote: > On 06/21/2013 02:10 PM, Yinghai Lu wrote: >> in this way we can keep all numa etc on the place when online ram, cpu, >> pci... >> >> For example if we have 32 sockets system, most time for boot is with >> *BIOS* >> instead of OS. In those kind of system boot is like this way: >> only first two sockets get booted from bios to OS. >> later use hot add every other two sockets. >> >> that will also make BIOS simpler, and it need to support hot-add for >> services purpose anyway. >> > Yes the hot add path was one option we looked at and it did shorten boot > times but the goal I had here is to get from power on to having the full > machine available as quick as possible. Several clients need significant > portions of ram for their key workloads. So that guided my thoughts on this > patch. you mean boot small number sockets + hot add still take more time? hot add ram still in serialize mode? Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists