Messages in this thread | | | Date | Wed, 18 Nov 2015 16:04:40 +0000 | From | Morten Rasmussen <> | Subject | Re: [PATCH 3/4] sched: introduce synchronized idle injection |
| |
On Wed, Nov 18, 2015 at 07:11:31AM -0800, Jacob Pan wrote: > On Wed, 18 Nov 2015 15:09:44 +0000 > Morten Rasmussen <morten.rasmussen@arm.com> wrote: > > > Okay. But it does mean that the defeault idle period is 5 ticks (50ms > > @ HZ=100) and not 5 ms > correct. my reason is to scale with various HZ values.
50ms seems quite long for embedded applications. OTOH, it has to be long enough to enter a package idle state and stay there for a while. You would surely notice it when it kicks in on an Android device.
Do you intend to use it only as a last option? One might want to keep using inefficient frequencies (P-states) if those don't cause UI lag then.
| |