Good news, thanks a lot!
On 03/01/2016 05:41 PM, Daniel P. Berrange wrote:
On Sat, Feb 27, 2016 at 01:47:38PM +0300, Alexander Burluka wrote:
On 02/26/2016 08:34 PM, Daniel P. Berrange wrote:
On Tue, Feb 16, 2016 at 04:43:32PM +0300, Alexander Burluka wrote:
This patchset implements an
On Sat, Feb 27, 2016 at 01:47:38PM +0300, Alexander Burluka wrote:
>
>
> On 02/26/2016 08:34 PM, Daniel P. Berrange wrote:
> >On Tue, Feb 16, 2016 at 04:43:32PM +0300, Alexander Burluka wrote:
> >>This patchset implements an ability to specify values for domain top level
> >>cpu.cfs_period_us
On 02/26/2016 08:34 PM, Daniel P. Berrange wrote:
On Tue, Feb 16, 2016 at 04:43:32PM +0300, Alexander Burluka wrote:
This patchset implements an ability to specify values for domain top level
cpu.cfs_period_us and cpu.cfs_quota_us cgroups. These parameters are opt-in
and named "global_period"
On Tue, Feb 16, 2016 at 04:43:32PM +0300, Alexander Burluka wrote:
> This patchset implements an ability to specify values for domain top level
> cpu.cfs_period_us and cpu.cfs_quota_us cgroups. These parameters are opt-in
> and named "global_period" and "global_quota".
>
> Introduction of these
This patchset implements an ability to specify values for domain top level
cpu.cfs_period_us and cpu.cfs_quota_us cgroups. These parameters are opt-in
and named "global_period" and "global_quota".
Introduction of these settings gives management applications further
choice of controlling CPU
