Re: [PATCH] sparc64: use latency groups to improve add_node_ranges speed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Pavel Tatashin <pasha.tatashin@xxxxxxxxxx>
Date: Thu, 16 Feb 2017 15:05:58 -0500

> add_node_ranges() takes 2.6s - 3.6s per 1T of boot time. On machine with 6T
> memory it takes 15.4s, on 32T it would take 82s-115s of boot time.
> This function sets NUMA ids for memory blocks, and scans the whole memory a
> page at a time to do so. But, we could use values in latency groups mask
> and match to determine the boundaries without checking every single page.
> With the fix the add_node_ranges() time is reduced from 15.4s down to 0.2s
> on machine with 6T memory.
> 
> Signed-off-by: Pavel Tatashin <pasha.tatashin@xxxxxxxxxx>
> Reviewed-by: Babu Moger <babu.moger@xxxxxxxxxx>
> Reviewed-by: Bob Picco <bob.picco@xxxxxxxxxx>

Applied.
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux