[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ffe4f4de-d433-91be-00ce-20b625807f20@arm.com>
Date: Thu, 5 Dec 2019 10:24:43 +0100
From: Dietmar Eggemann <dietmar.eggemann@....com>
To: Parth Shah <parth@...ux.ibm.com>, Qais Yousef <qais.yousef@....com>
Cc: linux-kernel@...r.kernel.org, peterz@...radead.org,
mingo@...hat.com, vincent.guittot@...aro.org,
patrick.bellasi@...bug.net, valentin.schneider@....com,
pavel@....cz, dhaval.giani@...cle.com, qperret@...rret.net,
David.Laight@...LAB.COM, morten.rasmussen@....com, pjt@...gle.com,
tj@...nel.org, viresh.kumar@...aro.org, rafael.j.wysocki@...el.com,
daniel.lezcano@...aro.org
Subject: Re: [RFC 3/3] Allow sched_{get,set}attr to change latency_tolerance
of the task
On 03/12/2019 16:51, Parth Shah wrote:
>
> On 12/3/19 2:09 PM, Qais Yousef wrote:
>> On 11/25/19 15:16, Parth Shah wrote:
[...]
>>> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
>>> index ea7abbf5c1bb..dfd36ec14404 100644
>>> --- a/kernel/sched/core.c
>>> +++ b/kernel/sched/core.c
>>> @@ -4695,6 +4695,9 @@ static void __setscheduler_params(struct task_struct *p,
>>> p->rt_priority = attr->sched_priority;
>>> p->normal_prio = normal_prio(p);
>>> set_load_weight(p, true);
>>> +
>>> + /* Change latency tolerance of the task if !SCHED_FLAG_KEEP_PARAMS */
IMHO, this comment seems to be gratuitous.
>>> + p->latency_tolerance = attr->sched_latency_tolerance;
>>> }
[...]
Powered by blists - more mailing lists