* Clark Williams | 2013-11-26 10:12:32 [-0600]: >In my experience (on x86_64 mainly), that behavior (worse times when >not under load) is due to the overhead of coming out of power-save/idle >states. When you've got a big load on the system and all the cores are >active, then the power-save logic and/or the idle logic doesn't kick in >and devices aren't being powered down. This is the case here, too. The overhead comming out of a deep power state plus the invalidated caches. >Do you know if your OMAP has power-save logic available? Alternatively >do you know how expensive the idle mechanism is? Have you tried booting >with idle=poll then measuring without a load? idle=pull is x86 only. Disable the complete PM stuff should solve the issue. You could go via arch_cpu_idle() to check what is used. The idle routine should come either via cpuidle_idle_call() or arm_pm_idle(). >Clark Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
