On 06/20/2018 10:46 PM, Peter Zijlstra wrote: > On Thu, May 31, 2018 at 12:42:20PM -0400, Waiman Long wrote: >> Thinking about isolcpus emulation, I now realize that it is more than >> just disabling load balancing. it also disables some kernel threads like >> kworker from running so that an userspace application can monopolize as >> much of a cpu as possible. Disabling kernel threads from running isn't >> that hard if it is only done once at boot time. it is trickier if we >> have to do it at run time. > Don't think it is all that difficult, we just need a notifier for when > that housekeeping thing changes and ensure that everybody who uses it > re-evaluates crap. Yes, it is certainly doable. I can work on that on my free time once the first cpuset v2 patch is done. There is enough complexity in the current patchset and I don't want to add stuff that is not a part of the core cpuset functionality at this point. We can also add new feature in the future, but once it is in, it is hard to change it. >> Without good isolcpus emulation, disabling load balance kind of loses >> its usefulness. So I am going to take out the load_balance flag for now >> unless I hear objection otherwise. > I'm not seeing the direct link between the load_balance flag and > isolcpus emulation in the proposed stuff. > > We can tie the housekeeping mask to whatever CPUs remain in the root > cgroup, couple that to that notifier and it should all just work I > think. The group of cpus in isolcpus are outside the reach of the scheduler and so is equivalent to turning off load balancing in that sense. Of course, there may also be other stuff that need to be considered in order to have a proper emulation of isolcpus. Cheers, Longman -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
