lkml.org 
[lkml]   [2018]   [Aug]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH v3 01/14] sched/core: uclamp: extend sched_setattr to support utilization clamping
    From
    Date
    Hi,

    On 08/06/2018 09:39 AM, Patrick Bellasi wrote:
    > diff --git a/init/Kconfig b/init/Kconfig
    > index 041f3a022122..1d45a6877d6f 100644
    > --- a/init/Kconfig
    > +++ b/init/Kconfig
    > @@ -583,6 +583,25 @@ config HAVE_UNSTABLE_SCHED_CLOCK
    > config GENERIC_SCHED_CLOCK
    > bool
    >
    > +menu "Scheduler features"
    > +
    > +config UCLAMP_TASK
    > + bool "Enable utilization clamping for RT/FAIR tasks"
    > + depends on CPU_FREQ_GOV_SCHEDUTIL
    > + default false

    default n
    but just omit the line completely since "n" is already the default.

    > + help
    > + This feature enables the scheduler to track the clamped utilization
    > + of each CPU based on RUNNABLE tasks currently scheduled on that CPU.
    > +
    > + When this option is enabled, the user can specify a min and max CPU
    > + bandwidth which is allowed for a task.
    > + The max bandwidth allows to clamp the maximum frequency a task can
    > + use, while the min bandwidth allows to define a minimum frequency a
    > + task will always use.

    Please clean up the indentation above to use one tab + 2 spaces on all lines.

    > +
    > + If in doubt, say N.
    > +
    > +endmenu


    thanks,
    --
    ~Randy

    \
     
     \ /
      Last update: 2018-08-06 18:52    [W:6.117 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site