From: Tommaso Cucinotta <tommaso.cucinotta@sssup.it>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <Juri.Lelli@arm.com>,
Robin Randhawa <robin.randhawa@arm.com>,
Steve Muckle <smuckle.linux@gmail.com>
Subject: Re: [PATCH 2/3] cpufreq: schedutil: move slow path from workqueue to SCHED_FIFO task
Date: Fri, 11 Nov 2016 15:32:04 +0100 [thread overview]
Message-ID: <d9caf98b-706d-d331-89c4-b75120589da3@sssup.it> (raw)
In-Reply-To: <85bf45982709e06f7f42e1b8f8315945e9d9b6d0.1478858983.git.viresh.kumar@linaro.org>
Hi,
On 11/11/2016 11:22, Viresh Kumar wrote:
> If slow path frequency changes are conducted in a SCHED_OTHER context
> then they may be delayed for some amount of time, including
> indefinitely, when real time or deadline activity is taking place.
>
> Move the slow path to a real time kernel thread. In the future the
> thread should be made SCHED_DEADLINE.
would you have an insight, as to what runtime/deadline/period to set, and/or
what specific timing constraints you'd like to set, just for this cpufreq
slowpath work?
> The RT priority is arbitrarily set
> to 50 for now.
[...]
> + struct sched_param param = { .sched_priority = 50 };
won't you have a tunable here? (sysctl?)
Thanks,
T.
--
Tommaso Cucinotta, Computer Engineering PhD
Associate Professor at the Real-Time Systems Laboratory (ReTiS)
Scuola Superiore Sant'Anna, Pisa, Italy
http://retis.sssup.it/people/tommaso
next prev parent reply other threads:[~2016-11-11 14:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 10:22 [PATCH 0/3] " Viresh Kumar
2016-11-11 10:22 ` [PATCH 1/3] cpufreq: schedutil: enable fast switch earlier Viresh Kumar
2016-11-11 14:19 ` Peter Zijlstra
2016-11-11 21:52 ` Rafael J. Wysocki
2016-11-11 22:55 ` Peter Zijlstra
2016-11-11 21:58 ` Rafael J. Wysocki
2016-11-12 5:19 ` Viresh Kumar
2016-11-13 14:46 ` Rafael J. Wysocki
2016-11-14 4:06 ` Viresh Kumar
2016-11-14 11:30 ` Viresh Kumar
2016-11-11 10:22 ` [PATCH 2/3] cpufreq: schedutil: move slow path from workqueue to SCHED_FIFO task Viresh Kumar
2016-11-11 14:32 ` Tommaso Cucinotta [this message]
2016-11-11 14:39 ` Peter Zijlstra
2016-11-12 5:22 ` Viresh Kumar
2016-11-14 9:22 ` Peter Zijlstra
2016-11-14 10:22 ` Viresh Kumar
2016-11-12 5:21 ` Viresh Kumar
2016-11-11 22:16 ` Rafael J. Wysocki
2016-11-12 1:31 ` Saravana Kannan
2016-11-12 5:27 ` Viresh Kumar
2016-11-14 5:37 ` Viresh Kumar
2016-11-13 14:37 ` Rafael J. Wysocki
2016-11-13 19:47 ` Steve Muckle
2016-11-13 22:44 ` Rafael J. Wysocki
2016-11-14 6:36 ` Viresh Kumar
2016-11-12 5:24 ` Viresh Kumar
2016-11-13 19:31 ` Steve Muckle
2016-11-11 10:22 ` [PATCH 3/3] cpufreq: schedutil: irq-work is used only in slow path Viresh Kumar
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=d9caf98b-706d-d331-89c4-b75120589da3@sssup.it \
--to=tommaso.cucinotta@sssup.it \
--cc=Juri.Lelli@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=robin.randhawa@arm.com \
--cc=smuckle.linux@gmail.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
all inboxes | Powered by JetHome®