All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
	Rafael Wysocki <rjw@rjwysocki.net>,
	Ingo Molnar <mingo@redhat.com>,
	Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <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: Sat, 12 Nov 2016 10:52:35 +0530	[thread overview]
Message-ID: <CAKohponr4=8Bf9C1=_YEhsvDXm0t2vXyGOnrrEr6HaMKzVOcnQ@mail.gmail.com> (raw)
In-Reply-To: <20161111143935.GK3117@twins.programming.kicks-ass.net>

On 11 November 2016 at 20:09, Peter Zijlstra <peterz@infradead.org> wrote:
> On Fri, Nov 11, 2016 at 03:32:04PM +0100, Tommaso Cucinotta wrote:
>> >+    struct sched_param param = { .sched_priority = 50 };
>>
>> won't you have a tunable here? (sysctl?)
>
> You can use the regular userspace tools, like schedtool and chrt to set
> priorities.

I wanted to get some help from you on this Peter. The out of tree Interactive
governor has always used MAX_RT_PRIORITY - 1 here instead of 50.

But Steve started with 50. What do you think should the value be ?

--
viresh

  reply	other threads:[~2016-11-12  5:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 10:22 [PATCH 0/3] cpufreq: schedutil: move slow path from workqueue to SCHED_FIFO task 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
2016-11-11 14:39     ` Peter Zijlstra
2016-11-12  5:22       ` Viresh Kumar [this message]
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='CAKohponr4=8Bf9C1=_YEhsvDXm0t2vXyGOnrrEr6HaMKzVOcnQ@mail.gmail.com' \
    --to=viresh.kumar@linaro.org \
    --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=tommaso.cucinotta@sssup.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.