anchor.diff:  
   * CPU affinity: It consists of binding a cgroup to certain CPU cores. The actual amount of CPU cycles that can be consumed by the cgroup is thus limited to what is available on the bound CPU cores.
   
  -* CPU bandwidth: Sets the weight of a cgroup with the process scheduler. The process scheduler divides the available CPU cycles among cgroups depending on the shares held by each cgroup, <em>relatively to the shares held by the others</em>. For example, consider two cgroups, one holding 2 shares and one holding 4. Assuming the process scheduler gets to administer 60 CPU cycles, the first cgroup with two shares will get one third of those available CPU cycles, as it holds one third of the overall shares. Similarly, the second cgroup will get 40 cycles, as it holds two thirds of the collective shares.
  +* CPU bandwidth: Sets the weight of a cgroup with the process scheduler. The process scheduler divides the available CPU cycles among cgroups depending on the shares held by each cgroup, relative to the shares held by the others.  
  +For example, consider two cgroups, one holding two shares and one holding four. Assuming the process scheduler gets to administer 60 CPU cycles, the first cgroup with two shares will get one third of those available CPU cycles, as it holds one third of the overall shares. Similarly, the second cgroup will get 40 cycles, as it holds two thirds of the collective shares.
   
   The calculation of the CPU usage based on the percentage of the total CPU power
   available is quite sophisticated and is performed regularly as the CPU demands
  
positive.code: a cgroup gets can be calculated by dividing the <code>cpu.shares</code> it holds by the sum
  of the <code>cpu.shares</code> of all the cgroups that are currently doing CPU activity:
  
  <code>process_cpu_share_percent = cpu.shares / sum_cpu_shares * 100</code>
  
  In Cloud Foundry, cgroup shares range from 2/10 (respecively for DEA/Diego) to
  1024, with 1024 being the default. The actual amount of shares a cgroup gets
  can be read from the <code>cpu.shares</code> of the c-group configurations
  pseudo-file-system located in the runner under the <code>/tmp/warden/cgroups</code> folder.
  
  The actual amount of shares given to a cgroup depends on the amount of memory
  the application declares to need in the manifest. Both Diego and DEA apps scale
  the number of allocated shares linearly with the amount of memory, with an app
  instance requesting 8G of memory getting the upper limit of 1024 shares. 
  
  <code>process_cpu.shares = max( (application_memory / 8), 1024)</code>
  
  The next example helps to illustrate this better. Consider three processes -
  P1, P2 and P3 and they are assigned respectively <code>cpu.shares</code> of 5, 20 and 30.
  P1 is active, while P2 and P3 require no CPU. Hence, P1 may use the whole CPU.
  When P2 joins in and is doing some actual work (e.g. a request comes in),
  the CPU share between P1 and P2 will be calculated as follows:
  
negative.code: * P2 -> 20 / (5+20+30) = 0.363 = ~36%
  * P3 -> 30 / (5+20+30) = 0.545 = ~55%
  
  Should P1 become idle, the following recalculation between P2 and P3
  takes place:
  
  * P1 (idle)
  