On Thu, May 12, 2016 at 6:36 PM, Steve Muckle steve.muckle@linaro.org wrote:
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.
Exactly.
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.
We can't really deprecate any out-of-the-tree code, because it is beyond the scope of our influence, so one can argue that taking it into the tree may actually allow us to deprecate it at one point going forward. :-)
Seriously, though, "deprecation" may not be the right term to use here. Our goal, IMO, should be to persuade the users of the code in question to switch over to something else and I'm not really sure if refusing to take that code into the tree is the best way to achieve that goal.
I do believe that if there's a significant piece of code living out of the tree for a sufficiently long time, the tree is likely to be missing something important. Then, it is really difficult to figure out what is missing without even trying to take that code into the tree.