Thread (30 messages) 30 messages, 2 authors, 2019-06-05

Re: [PATCH v9 12/16] sched/core: uclamp: Extend CPU's cgroup controller

From: Tejun Heo <tj@kernel.org>
Date: 2019-06-05 15:39:59
Also in: linux-pm, lkml

Hello, Patrick.

On Wed, Jun 05, 2019 at 04:37:43PM +0100, Patrick Bellasi wrote:
quoted
Everything sounds good to me.  Please note that cgroup interface files
actually use literal "max" for limit/protection max settings so that 0
and "max" mean the same things for all limit/protection knobs.
Lemme see if I've got it right, do you mean that we can:

 1) write the _string_ "max" into a cgroup attribute to:

    - set    0 for util_max, since it's a protection
    - set 1024 for util_min, since it's a limit

 2) write the _string_ "0" into a cgroup attribute to:

    - set 1024 for util_max, since it's a protection
    - set    0 for util_min, since it's a limit

Is that correct or it's just me totally confused?
Heh, sorry about not being clearer.  "max" just means numerically
highest possible config for the config knob, so in your case, "max"
would always map to 1024.

Thanks.

-- 
tejun
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help