Reconsidering the scheduler's wake_wide() heuristic
Reconsidering the scheduler's wake_wide() heuristic
Posted Jul 29, 2017 9:31 UTC (Sat) by garloff (subscriber, #319)In reply to: Reconsidering the scheduler's wake_wide() heuristic by ejr
Parent article: Reconsidering the scheduler's wake_wide() heuristic
So, it indeed seems that an application should tell the kernel how hard it should try to place communicating processes close to each other. Probably should not be binary, but allow for different steps.
Question is whether this can be done efficiently at process group scope or whether it needs to be system-wide. Maybe Cgroup-wide?
Question is whether this can be done efficiently at process group scope or whether it needs to be system-wide. Maybe Cgroup-wide?