From: Parth Shah <parth@linux.ibm.com>
To: Qais Yousef <qais.yousef@arm.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, vincent.guittot@linaro.org,
patrick.bellasi@matbug.net, valentin.schneider@arm.com,
pavel@ucw.cz, dhaval.giani@oracle.com, qperret@qperret.net,
David.Laight@ACULAB.COM, morten.rasmussen@arm.com,
pjt@google.com, tj@kernel.org, dietmar.eggemann@arm.com,
viresh.kumar@linaro.org, rafael.j.wysocki@intel.com,
daniel.lezcano@linaro.org
Subject: Re: [RFC 3/3] Allow sched_{get,set}attr to change latency_tolerance of the task
Date: Tue, 3 Dec 2019 21:21:55 +0530 [thread overview]
Message-ID: <cfb607c1-6be9-853d-cfad-6787f78fa6ad@linux.ibm.com> (raw)
In-Reply-To: <20191203083915.yahl2qd3wnnkqxxs@e107158-lin.cambridge.arm.com>
On 12/3/19 2:09 PM, Qais Yousef wrote:
> On 11/25/19 15:16, Parth Shah wrote:
>> Introduce the latency_tolerance attribute to sched_attr and provide a
>> mechanism to change the value with the use of sched_setattr/sched_getattr
>> syscall.
>>
>> Also add new flag "SCHED_FLAG_LATENCY_TOLERANCE" to hint the change in
>> latency_tolerance of the task on every sched_setattr syscall.
>>
>> Signed-off-by: Parth Shah <parth@linux.ibm.com>
>> ---
>> include/uapi/linux/sched.h | 4 +++-
>> include/uapi/linux/sched/types.h | 2 ++
>> kernel/sched/core.c | 15 +++++++++++++++
>> kernel/sched/sched.h | 1 +
>> 4 files changed, 21 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/uapi/linux/sched.h b/include/uapi/linux/sched.h
>> index b3105ac1381a..73db430d11b6 100644
>> --- a/include/uapi/linux/sched.h
>> +++ b/include/uapi/linux/sched.h
>> @@ -71,6 +71,7 @@ struct clone_args {
>> #define SCHED_FLAG_KEEP_PARAMS 0x10
>> #define SCHED_FLAG_UTIL_CLAMP_MIN 0x20
>> #define SCHED_FLAG_UTIL_CLAMP_MAX 0x40
>> +#define SCHED_FLAG_LATENCY_TOLERANCE 0x80
>>
>> #define SCHED_FLAG_KEEP_ALL (SCHED_FLAG_KEEP_POLICY | \
>> SCHED_FLAG_KEEP_PARAMS)
>> @@ -82,6 +83,7 @@ struct clone_args {
>> SCHED_FLAG_RECLAIM | \
>> SCHED_FLAG_DL_OVERRUN | \
>> SCHED_FLAG_KEEP_ALL | \
>> - SCHED_FLAG_UTIL_CLAMP)
>> + SCHED_FLAG_UTIL_CLAMP | \
>> + SCHED_FLAG_LATENCY_TOLERANCE)
>>
>> #endif /* _UAPI_LINUX_SCHED_H */
>> diff --git a/include/uapi/linux/sched/types.h b/include/uapi/linux/sched/types.h
>> index c852153ddb0d..960774ac0c70 100644
>> --- a/include/uapi/linux/sched/types.h
>> +++ b/include/uapi/linux/sched/types.h
>> @@ -118,6 +118,8 @@ struct sched_attr {
>> __u32 sched_util_min;
>> __u32 sched_util_max;
>>
>> + /* latency requirement hints */
>> + __s32 sched_latency_tolerance;
>> };
>>
>> #endif /* _UAPI_LINUX_SCHED_TYPES_H */
>> 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 */
>> + p->latency_tolerance = attr->sched_latency_tolerance;
>> }
>>
>> /* Actually do priority change: must hold pi & rq lock. */
>> @@ -4852,6 +4855,13 @@ static int __sched_setscheduler(struct task_struct *p,
>> return retval;
>> }
>>
>> + if (attr->sched_flags & SCHED_FLAG_LATENCY_TOLERANCE) {
>> + if (attr->sched_latency_tolerance > MAX_LATENCY_TOLERANCE)
>> + return -EINVAL;
>> + if (attr->sched_latency_tolerance < MIN_LATENCY_TOLERANCE)
>> + return -EINVAL;
>> + }
>> +
>> if (pi)
>> cpuset_read_lock();
>>
>> @@ -4886,6 +4896,9 @@ static int __sched_setscheduler(struct task_struct *p,
>> goto change;
>> if (attr->sched_flags & SCHED_FLAG_UTIL_CLAMP)
>> goto change;
>> + if (attr->sched_flags & SCHED_FLAG_LATENCY_TOLERANCE &&
>> + attr->sched_latency_tolerance != p->latency_tolerance)
>> + goto change;
>>
>> p->sched_reset_on_fork = reset_on_fork;
>> retval = 0;
>> @@ -5392,6 +5405,8 @@ SYSCALL_DEFINE4(sched_getattr, pid_t, pid, struct sched_attr __user *, uattr,
>> else
>> kattr.sched_nice = task_nice(p);
>>
>> + kattr.sched_latency_tolerance = p->latency_tolerance;
>> +
>> #ifdef CONFIG_UCLAMP_TASK
>> kattr.sched_util_min = p->uclamp_req[UCLAMP_MIN].value;
>> kattr.sched_util_max = p->uclamp_req[UCLAMP_MAX].value;
>> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
>> index 0db2c1b3361e..bb181175954b 100644
>> --- a/kernel/sched/sched.h
>> +++ b/kernel/sched/sched.h
>> @@ -21,6 +21,7 @@
>> #include <linux/sched/nohz.h>
>> #include <linux/sched/numa_balancing.h>
>> #include <linux/sched/prio.h>
>> +#include <linux/sched/latency_tolerance.h>
>
> nit: keep in alphabatical order.
ok.
>
> The series looks good to me except for the 2 minor nits. Thanks for taking care
> of this!
My pleasure. Infact, I'm trying to write patches around what Subhra posted
for reducing wakeup scans https://lkml.org/lkml/2019/8/30/829 and few ideas
from Peter's patch https://lkml.org/lkml/2018/5/30/632. Aim here is to
reduce scans for lower latency_tolerance tasks and will post out soon which
uses this feature.
>
> Reviewed-by: Qais Yousef <qais.yousef@arm.com>
Thanks. Will add it.
>
> Cheers
>
> --
> Qais Yousef
>
>> #include <linux/sched/rt.h>
>> #include <linux/sched/signal.h>
>> #include <linux/sched/smt.h>
>> --
>> 2.17.2
>>
next prev parent reply other threads:[~2019-12-03 15:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 9:46 [RFC 0/3] Introduce per-task latency_tolerance for scheduler hints Parth Shah
2019-11-25 9:46 ` [RFC 1/3] Introduce latency-tolerance as an per-task attribute Parth Shah
2019-12-03 8:36 ` Qais Yousef
2019-12-03 15:47 ` Parth Shah
2019-12-05 9:24 ` Dietmar Eggemann
2019-12-05 11:42 ` Parth Shah
2019-11-25 9:46 ` [RFC 2/3] Propagate parent task's latency requirements to the child task Parth Shah
2019-11-25 9:46 ` [RFC 3/3] Allow sched_{get,set}attr to change latency_tolerance of the task Parth Shah
2019-12-03 8:39 ` Qais Yousef
2019-12-03 15:51 ` Parth Shah [this message]
2019-12-05 9:24 ` Dietmar Eggemann
2019-12-06 16:04 ` Dietmar Eggemann
2019-12-08 5:52 ` Parth Shah
2019-12-05 9:24 ` [RFC 0/3] Introduce per-task latency_tolerance for scheduler hints Dietmar Eggemann
2019-12-05 10:49 ` Valentin Schneider
2019-12-05 14:03 ` Dietmar Eggemann
2019-12-05 17:13 ` Parth Shah
2019-12-06 12:31 ` Dietmar Eggemann
2019-12-08 5:57 ` Parth Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfb607c1-6be9-853d-cfad-6787f78fa6ad@linux.ibm.com \
--to=parth@linux.ibm.com \
--cc=David.Laight@ACULAB.COM \
--cc=daniel.lezcano@linaro.org \
--cc=dhaval.giani@oracle.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@matbug.net \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=qais.yousef@arm.com \
--cc=qperret@qperret.net \
--cc=rafael.j.wysocki@intel.com \
--cc=tj@kernel.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).