Re: [PATCH] cobalt/sched-quota: Account for already consumed time on limit update

2018-11-26 Thread Jan Kiszka via Xenomai
On 26.11.18 13:22, Jan Kiszka wrote: On 25.11.18 18:14, Philippe Gerum wrote: On 11/21/18 5:59 PM, Jan Kiszka wrote: If we change the quota value of thread group, we should take its already consumed time during the current cycle into account. So far, we refilled the budget blindly, which could

Re: [PATCH] cobalt/sched-quota: Account for already consumed time on limit update

2018-11-26 Thread Jan Kiszka via Xenomai
On 25.11.18 18:14, Philippe Gerum wrote: On 11/21/18 5:59 PM, Jan Kiszka wrote: If we change the quota value of thread group, we should take its already consumed time during the current cycle into account. So far, we refilled the budget blindly, which could have given the group an uncontrolled

[PATCH] cobalt/sched-quota: Account for already consumed time on limit update

2018-11-25 Thread Philippe Gerum via Xenomai
On 11/21/18 5:59 PM, Jan Kiszka wrote: > If we change the quota value of thread group, we should take its already > consumed time during the current cycle into account. So far, we refilled > the budget blindly, which could have given the group an uncontrolled > "peak". > > This commit first

[PATCH] cobalt/sched-quota: Account for already consumed time on limit update

2018-11-21 Thread Jan Kiszka via Xenomai
If we change the quota value of thread group, we should take its already consumed time during the current cycle into account. So far, we refilled the budget blindly, which could have given the group an uncontrolled "peak". This commit first update the run_budget_ns of an active group and kills