On Thu, Mar 31, 2016 at 10:53:02AM -0700, bseg...@google.com wrote: > Yuyang Du <yuyang...@intel.com> writes: > > > The increased load resolution (fixed point arithmetic range) is > > unconditionally deactivated with #if 0, so it is effectively broken. > > > > But the increased load range is still used somewhere (e.g., in Google), > > so we keep this feature. The reconciliation is we define > > CONFIG_CFS_INCREASE_LOAD_RANGE and it depends on FAIR_GROUP_SCHED and > > 64BIT and BROKEN. > > > > Suggested-by: Ingo Molnar <mi...@kernel.org> > > Signed-off-by: Yuyang Du <yuyang...@intel.com> > > The title of this patch "Remove unconditionally inactive code" is > misleading since it's more like giving it a CONFIG.
Reasonable argument. > > Also as a side note, does anyone remember/have a test for whatever got > it turned off to begin with, given all the changes in load tracking and > the load balancer and everything else? It is this commit that turned it off: Commit e4c2fb0d5776: "sched: Disable (revert) SCHED_LOAD_SCALE increase"
