[Sprint Samsung Galaxy S III] mw86:
Fair enough. Ktoonservative from what i understand remember asking Ktoonsez it shuts core 2 off or hotplugs when both cores enter the minimum of atleast one cpu frequency bin above minimum. You used Ktoonservative base and added more tunables or rather adjusted function of some of them?

I can see one downfall to race to idle and that is in some cases idle will never happen as in its a process that continues on and off or consistently a load... since finishing the process isnt and option no matter how fast its calculated eventually speed in that scenario in an exponential way adds to unnecessary power draw.

Leaning as much as possible to higher performance imo from what i have read could actually equate to more power savings vs low power but slower completion times. Obviously as I just was hinting at... if higher speed used takes three to for times the power a slower mhz might take its questionable then if the frequency should be used. So in our phones lets just say the stock max is the nominal frequency before the power requirements outway the speed hypothetically. The max frequency has the potential to calculate a proposed load at as exageration 20 watt/sec and the mid frequency seems to take 5 watts a second and is very efficient. Lets say we put a load on both scenarios. Its possible that even though per second more watts are being drawn for the higher frequency per sec vs the lower that when it comes to crunch time the higher frequency may finish the work in 1/10 of a second and the lower half as fast at 1/2 a second. The faster drawing less watts over time. 2.5 watts for the lower frequency in this scenario and 2 watts for the higher frequency. Who is to say the cpu is that efficient... Who is to say our cpus are that efficient. As long as limits are kept like using only speeds which don't require more power than the potential work they can accomplish, there should be no problem using high frequencies for short times while staying at low power drain.

Nothing is perfect in every scenario and high performance tuned is one of those that creates a problem after addressing another. For racing to idle in short term and long term workloads that are not renuable (when workload is done and does not return) it can be found to benifit 100% from using a higher speed based on the above hypothetical scenario. When a workload is something that is not work to be completed but rather to be kept up on we see the one reason brite force is not the answer. Max frequency no matter what the frequency calculating load lets say on a song file it is playing will always be drawing power that is being wasted. It can calulate load as fast as possible but it doesnt stop.

This seems to say you could accomplish a fix by changingy suggestion above. Using maybe 2-4 transitions would be better. In 96-2106mhz having the jump to 96-500-1000-1500-2100 would be beneficial. Or even just 96-1000-2100 or 96-500-1000-1500. Using same thresholds you would see loads like browsing messaging and media hovering at low to medium speeds and not drop unless load dropped enough hence the 12% down Threshold. Low sample rate ie faster will allow quick ramp up. Too fast and its going to adjust speed when the load reading hasnt had the time to adjust to the new work load as a result of looking to change cpu speed based on cpu load too often. In most cases especially after checking out wheatley fast switching based on load can save power by not working when it doesnt need to. Getting back to a point if load is not going to go away cpu is better off at the cpus most power efficient frequency. Like 500-1000mhz for browsing mp3. The way i had thresholds you would see on mp3 it wpuld hit my 25% @96mhz and core two will pop on and then load would climb to 49% so about half load on each core or half of one core... the frequency would go to 500mhz for example at 25% frequency step and would stay there until the song stopped playing since cpu load would not drop likely to 12%. If load went over 49% again it would go to 1000mhz and again stay until load either equaled over 49% or under 12%... the later would return cpu to the 500mhz or 96mhz. Since hot plugging is built into ktoonservative as soon as cpu returns to 96mhz or even 144 in this scenario though 144 wouldnt show up with that scaling... core two is shut off then or hotplugged.

I have tried configs with conservative settings and forcing it to use smaller steps and found it needed not to go through so many transotoons to accomplish the goal as you see and I see that in the way you designed the governor. Does yours shut off the cores different from Ktoonservative? Also whats the lowest power state and how does hotplugging differ?

The above file labled aosp is Kt747 the entire kernel but with your governor added? Are all your parameters tunable or are some tunable and some locked to a value?

I think I/O busy and others can be important too as the system will get no where transfering files on lowest speeds vs higher and in most cases based on cpu load alone... cpu load can be low and i/o very busy and while on an on demand type governor the i/o gets bottle necked by the cpu. Many basic sd card tests yield sporadic results do to frquency often returning to minimum or near minimum frequency.

Id like to try your governor and see how i can take my idea and maybe accomplish better use of having cores off once idle or near idle is accomploshed. And perhaps keeping atleast one transition from min to max since 12% down threshold protects the user experience from sudden dips in cpu usage and therefore cpu speed and having a large span between that and up threshold protects the phone and user from using speeds unecessarily.

Essentially this design is almost like stock msdmvcs or whatever the name... Qualcomms governor. It goes in a few hundred mhz steps. But this way hotplugging and extreme fast decision rate based on 10ms sample times can be used to. Thats how i been tinkering and theorizing and ill gladly see how DMservative can improve upon the goal I have in mind.

Sounds like for powersavings and not high performance like i plan to tune for... You governor has potential. Ill give it ago tommorow so I can understand fully how you have designed it. Ill understand better seeing all the tunables at once.

Paranoid Galaxy S3 on Tapatalk 2