[lkml]   [2009]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC v2 PATCH 0/8] CFS Hard limits - v2
> IMO Pavel's requirement can be met with a hard limit of 25%
> 2 CPU of 1GHz = (1/2 x 4) (1/2 x 2) GHz CPUs
> = 1/4 x 4 2GHz CPU
> = 25% of (4 2GHz CPU)
> IOW by hard-limiting a container thread to run just 0.5sec every sec on a 2GHz
> cpu, it is effectively making progress at the rate of 1GHz?

So, any suggestions on this? I'm not against the patches themselves.
I'm just trying to tell, that setting a cpulimit with 2 numbers is
not a good way to go (at least a clean explanation of how to calculate
them should go with the patches).

I propose to first collect what *can* be done. I see the following

1) two times (as it is now) - I believe this is inconvenient.
2) the amount in percents (like 50%) - this is how it works in
OpenVZ and customers are quite happy with it. It's better than
two numbers, since you need to specify only one clean number.
3) virtual cpu power in M/GHz - I don't agree with Balbir that
this is difficult for administrator. This is better than two
numbers and better that the percentage, since the amount of
cpu time got by a container will not change after migrating to
a more powerful CPU.


> - vatsa

 \ /
  Last update: 2009-10-13 13:47    [W:0.073 / U:10.836 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site