We need to provide an ability to cap CPU usage for projects and zones in a non-contended
case. The FSS scheduling class today only caps CPU usage if projects and/or zones
compete for the same set of CPUs. New resource controls, namely zone.cpu-cap, and
project.cpu-cap will be introduced to control CPU consumption. Threads running
in projects and/or zones that have used all of their allocated CPU resources will be
put on special wait queues until CPU usage drops below specified cap levels. The values of zone.cpu-cap and project.cpu-cap resource controls will be expressed in terms of
absolute CPU percentage points. That is, 100 means one full CPU, 200 means two full
CPUs and so on.