> > Short summary: turning on CONFIG_NO_HZ_FULL_ALL seems to disable all > > non-boot CPUs for scheduler.
[...] > This is expected and intended behavior. The whole point of > CONFIG_NO_HZ_FULL_ALL is to keep everything off of the non-boot CPUs > that is not explicitly placed there. Without CONFIG_NO_HZ_FULL_ALL, > you can use the nohz_full boot parameter to select exactly which > CPUs are to behave this way. OK, thanks - disabled it on my desktops anyway now. Perhaps the Kconfig description of it should explian the consequences more clearly so other people do not stumble upon it like I did? -- Meelis Roos ([email protected]) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
