Thanks. I went through a few iterations until finalizing on the current patches. Originally the memory was inserted using the memory probe interface, but at 2G per addition, it was still very slow. By bypassing the memory driver interface, and going directly to add_memory and memory_online, along with Nathan's changes to unlock the memory mutex on a per node basis, it sped up dramatically. On 6/25/2013 8:07 AM, H. Peter Anvin wrote: > I have to say I really like this concept. It should have some very nice properties including perhaps making THP work better? > > Ingo Molnar <mingo@xxxxxxxxxx> wrote: > >> >> * Nathan Zimmer <nzimmer@xxxxxxx> wrote: >> >>> On Sun, Jun 23, 2013 at 11:28:40AM +0200, Ingo Molnar wrote: >>>> >>>> That's 4.5 GB/sec initialization speed - that feels a bit slow and >> the >>>> boot time effect should be felt on smaller 'a couple of gigabytes' >>>> desktop boxes as well. Do we know exactly where the 2 hours of boot >> >>>> time on a 32 TB system is spent? >>> >>> There are other several spots that could be improved on a large >> system >>> but memory initialization is by far the biggest. >> >> My feeling is that deferred/on-demand initialization triggered from the >> >> buddy allocator is the better long term solution. >> >> That will also make it much easier to profile/test memory init >> performance: boot up a large system and run a simple testprogram that >> allocates a lot of RAM. >> >> ( It will also make people want to optimize the initialization sequence >> >> better, as it will be part of any freshly booted system's memory >> allocation overhead. ) >> >> Thanks, >> >> Ingo > -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
