On Sun, Apr 04, 2021 at 10:51:53PM +0800, yulei.kernel@xxxxxxxxx wrote: > From: Yulei Zhang <yuleixzhang@xxxxxxxxxxx> > > This patch is the init patch of a series which we want to present the idea > of prioritized tasks management. As the cloud computing introduces intricate > configurations to provide customized infrasturctures and friendly user > experiences, in order to maximum utilization of sources and improve the > efficiency of arrangement, we add the new attribute "priority" to control > group, which could be used as graded factor by subssystems to manipulate > the behaviors of processes. > > Base on the order of priority, we could apply different resource configuration > strategies, sometimes it will be more accuracy instead of fine tuning in each > subsystem. And of course to set fundamental rules, for example, high priority > cgroups could seize the resource from cgroups with lower priority all the time. > > The default value of "priority" is set to 0 which means the highest > priority, and the totally levels of priority is defined by > CGROUP_PRIORITY_MAX. Each subsystem could register callback to receive the > priority change notification for their own purposes. > > We would like to send out the corresponding features in the coming weeks, > which are relaying on the priority settings. For example, the prioritized > oom, memory reclaiming and cpu schedule strategy. We've been trying really hard to give each interface semantics which is logical and describable independent of the implementation details. This runs precisely against that. Thanks. -- tejun
