Print this page
6591 resource_controls(5) should talk about project.cpu-cap not project.cpu-caps


  93 
  94 
  95        process.max-sem-ops
  96 
  97            Maximum number of semaphore operations allowed per semop call
  98            (value copied from the resource control at semget() time).
  99            Expressed as an integer, specifying the number of operations.
 100 
 101 
 102        process.max-sigqueue-size
 103 
 104            Maximum number of outstanding queued signals.
 105 
 106 
 107        process.max-stack-size
 108 
 109            Maximum stack memory segment available to this process, expressed
 110            as a number of bytes.
 111 
 112 
 113        project.cpu-caps
 114 
 115            Maximum amount of CPU resources that a project can use. The unit
 116            used is the percentage of a single CPU that can be used by all user
 117            threads in a project.  Expressed as an integer. The cap does not
 118            apply to threads running in real-time scheduling class. This
 119            resource control does not support the syslog action.
 120 
 121 
 122        project.cpu-shares
 123 
 124            Number of CPU shares granted to a project for use with the fair
 125            share scheduler (see FSS(7)). The unit used is the number of shares
 126            (an integer). This resource control does not support the syslog
 127            action.
 128 
 129 
 130        project.max-contracts
 131 
 132            Maximum number of contracts allowed in a project, expressed as an
 133            integer.




  93 
  94 
  95        process.max-sem-ops
  96 
  97            Maximum number of semaphore operations allowed per semop call
  98            (value copied from the resource control at semget() time).
  99            Expressed as an integer, specifying the number of operations.
 100 
 101 
 102        process.max-sigqueue-size
 103 
 104            Maximum number of outstanding queued signals.
 105 
 106 
 107        process.max-stack-size
 108 
 109            Maximum stack memory segment available to this process, expressed
 110            as a number of bytes.
 111 
 112 
 113        project.cpu-cap
 114 
 115            Maximum amount of CPU resources that a project can use. The unit
 116            used is the percentage of a single CPU that can be used by all user
 117            threads in a project.  Expressed as an integer. The cap does not
 118            apply to threads running in real-time scheduling class. This
 119            resource control does not support the syslog action.
 120 
 121 
 122        project.cpu-shares
 123 
 124            Number of CPU shares granted to a project for use with the fair
 125            share scheduler (see FSS(7)). The unit used is the number of shares
 126            (an integer). This resource control does not support the syslog
 127            action.
 128 
 129 
 130        project.max-contracts
 131 
 132            Maximum number of contracts allowed in a project, expressed as an
 133            integer.