From: Steve Muckle <steve.muckle@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
Ingo Molnar <mingo@kernel.org>,
Morten Rasmussen <Morten.Rasmussen@arm.com>,
Juri Lelli <juri.lelli@arm.com>,
Steve Muckle <steve.muckle@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [RFC] Should we add Android's Interactive governor into mainline now?
Date: Thu, 12 May 2016 09:36:48 -0700 [thread overview]
Message-ID: <20160512163648.GB12886@graphite.smuckle.net> (raw)
In-Reply-To: <CAKohponvfRR=nDPcVWpW0L1JZO9+7hgLL7YrWwyJXkL8BtJNpg@mail.gmail.com>
On Thu, May 12, 2016 at 07:34:01AM +0530, Viresh Kumar wrote:
> Since we have moved away from the background timers to scheduler
> callbacks, should we consider merging the Interactive governor into
> mainline ?
Merging interactive will help us more easily compare schedutil against
it and get schedutil at or beyond feature parity.
That said my understanding is that the goal is to eventually deprecate
the non-sched governors. That will be made harder by adding another one
into the tree.
next prev parent reply other threads:[~2016-05-12 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 2:04 [RFC] Should we add Android's Interactive governor into mainline now? Viresh Kumar
2016-05-12 13:19 ` Rafael J. Wysocki
2016-05-13 3:19 ` Viresh Kumar
2016-05-13 11:06 ` Rafael J. Wysocki
2016-05-13 11:09 ` Viresh Kumar
2016-05-12 16:36 ` Steve Muckle [this message]
2016-05-12 20:34 ` Rafael J. Wysocki
2016-05-12 21:10 ` Steve Muckle
2016-05-13 3:21 ` Viresh Kumar
2016-05-13 6:14 ` Steve Muckle
2016-05-13 6:17 ` Viresh Kumar
2016-05-13 11:44 ` Juri Lelli
2016-05-13 11:56 ` Rafael J. Wysocki
2016-05-13 13:15 ` 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=20160512163648.GB12886@graphite.smuckle.net \
--to=steve.muckle@linaro.org \
--cc=Morten.Rasmussen@arm.com \
--cc=juri.lelli@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--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