[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a19be99d1e1a282bd5c6b9af60ea6c0417223000.camel@linux.intel.com>
Date: Mon, 21 Mar 2022 17:22:32 -0700
From: Tim Chen <tim.c.chen@...ux.intel.com>
To: Vincent Guittot <vincent.guittot@...aro.org>, mingo@...hat.com,
peterz@...radead.org, juri.lelli@...hat.com,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, linux-kernel@...r.kernel.org, parth@...ux.ibm.com
Cc: qais.yousef@....com, chris.hyser@...cle.com,
pkondeti@...eaurora.org, valentin.schneider@....com,
patrick.bellasi@...bug.net, David.Laight@...lab.com,
pjt@...gle.com, pavel@....cz, tj@...nel.org,
dhaval.giani@...cle.com, qperret@...gle.com
Subject: Re: [PATCH 2/6] sched/core: Propagate parent task's latency
requirements to the child task
On Fri, 2022-03-11 at 17:14 +0100, Vincent Guittot wrote:
>
> Signed-off-by: Vincent Guittot <vincent.guittot@...aro.org>
> ---
> init/init_task.c | 1 +
> kernel/sched/core.c | 4 ++++
> 2 files changed, 5 insertions(+)
>
> diff --git a/init/init_task.c b/init/init_task.c
> index 73cc8f03511a..2afa249c253b 100644
> --- a/init/init_task.c
> +++ b/init/init_task.c
> @@ -78,6 +78,7 @@ struct task_struct init_task
> .prio = MAX_PRIO - 20,
> .static_prio = MAX_PRIO - 20,
> .normal_prio = MAX_PRIO - 20,
> + .latency_nice = 0,
Probably better to use non hardcoded number here
.latency_nice = DEFAULT_LATENCY_NICE;
> .policy = SCHED_NORMAL,
> .cpus_ptr = &init_task.cpus_mask,
> .user_cpus_ptr = NULL,
>
Tim
Powered by blists - more mailing lists