On 03/09/2018 02:40 PM, Mike Galbraith wrote: >>> >>> If v2 is to ever supersede v1, as is the normal way of things, core >>> functionality really should be on the v2 boat when it sails. What you >>> left standing on the dock is critical core cpuset functionality. >>> >>> -Mike >> From your perspective, what are core functionality that should be >> included in cpuset v2 other than the ability to restrict cpus and memory >> nodes. > Exclusive sets are essential, no? How else can you manage set wide > properties such as topology (and hopefully soonish nohz). You clearly > can't have overlapping sets, one having scheduler topology, the other > having none. Whatever the form, something as core as the capability to > dynamically partition and isolate should IMO be firmly aboard the v2 > boat before it sails. > > -Mike The isolcpus= parameter just reduce the cpus available to the rests of the system. The cpuset controller does look at that value and make adjustment accordingly, but it has no dependence on exclusive cpu/mem features of cpuset. -Longman -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
