From: Atish Patra <atish.patra@xxxxxxxxxx> Date: Wed, 19 Oct 2016 18:33:29 -0600 > Individual scheduler domain should consist different hierarchy > consisting of cores sharing similar property. Currently, no > scheduler domain is defined separately for the cores that shares > the last level cache. As a result, the scheduler fails to take > advantage of cache locality while migrating tasks during load > balancing. > > Here are the cpu masks currently present for sparc that are/can > be used in scheduler domain construction. > cpu_core_map : set based on the cores that shares l1 cache. > core_core_sib_map : is set based on the socket id. > The prior SPARC notion of socket was defined as highest level of > shared cache. However, the MD record on T7 platforms now describes > the CPUs that share the physical socket and this is no longer tied > to shared cache. > > That's why a separate cpu mask needs to be created that truly > represent highest level of shared cache for all platforms. > > Signed-off-by: Atish Patra <atish.patra@xxxxxxxxxx> > Reviewed-by: Chris Hyser <chris.hyser@xxxxxxxxxx> Applied, thank you. -- 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
