From: Qais Yousef <qyousef@layalina.io>
To: Christian Loehle <christian.loehle@arm.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] sched/cpufreq: Use USEC_PER_SEC for deadline task
Date: Fri, 9 Aug 2024 02:24:10 +0100 [thread overview]
Message-ID: <20240809012410.marjxrio3sjequnn@airbuntu> (raw)
In-Reply-To: <3c726cf5-0c94-4cc6-aff0-a453d840d452@arm.com>
Adding more sched folks to CC
On 08/06/24 14:41, Christian Loehle wrote:
> Convert the sugov deadline task attributes to use the available
> definitions to make them more readable.
> No functional change.
>
> Signed-off-by: Christian Loehle <christian.loehle@arm.com>
> ---
> kernel/sched/cpufreq_schedutil.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
> index eece6244f9d2..012b38a04894 100644
> --- a/kernel/sched/cpufreq_schedutil.c
> +++ b/kernel/sched/cpufreq_schedutil.c
> @@ -654,9 +654,9 @@ static int sugov_kthread_create(struct sugov_policy *sg_policy)
> * Fake (unused) bandwidth; workaround to "fix"
> * priority inheritance.
> */
> - .sched_runtime = 1000000,
> - .sched_deadline = 10000000,
> - .sched_period = 10000000,
> + .sched_runtime = USEC_PER_SEC,
> + .sched_deadline = 10 * USEC_PER_SEC,
> + .sched_period = 10 * USEC_PER_SEC,
I think NSEC_PER_MSEC is the correct one. The units in
include/uapi/linux/sched/types.h is not specified. Had to look at
sched-deadline.rst to figure it out.
Assuming I didn't get it wrong, mind adding the unit to types.h too?
Thanks!
--
Qais Yousef
> };
> struct cpufreq_policy *policy = sg_policy->policy;
> int ret;
> --
> 2.34.1
next prev parent reply other threads:[~2024-08-09 1:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 13:41 Christian Loehle
2024-08-09 1:24 ` Qais Yousef [this message]
2024-08-09 7:42 ` Juri Lelli
2024-08-13 7:54 ` Vincent Guittot
2024-08-13 10:17 ` Christian Loehle
2024-08-13 13:19 ` Juri Lelli
2024-08-13 13:34 ` Christian Loehle
2024-08-13 13:57 ` Juri Lelli
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=20240809012410.marjxrio3sjequnn@airbuntu \
--to=qyousef@layalina.io \
--cc=christian.loehle@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@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
all inboxes | Powered by JetHome®