On 12 April 2018 at 20:22, Peter Zijlstra <pet...@infradead.org> wrote: > On Tue, Apr 10, 2018 at 02:19:50PM +0100, Morten Rasmussen wrote: >> As said above, I see your point about completion time might suffer in >> some cases for low utilization tasks, but I don't see how you can fix >> that automagically. ASYM_PACKING has a lot of problematic side-effects. >> If use-space knows that completion time is important for a task, there >> are already ways to improve that somewhat in mainline (task priority and >> pinning), and more powerful solutions in the Android kernel which >> Patrick is currently pushing upstream. > > So I tend to side with Morten on this one. I don't particularly like > ASYM_PACKING much, but we already had it for PPC and it works for the > small difference in performance ITMI has. > > At the time Morten already objected to using it for ITMI, and I just > haven't had time to look into his proposal for using capacity. > > But I don't see it working right for big.litte/dynamiq, simply because > it is a very strong always big preference, which is against the whole > design premisis of big.little (as Morten has been trying to argue).
In fact, Little not only gives some better power efficiency but it also handles far better some stuff like interrupt handling as an example Nevertheless, whatever the solution, it will never fit with big.Little/dynamiQ system without some EAS as soon as the power efficiency is involved in the equation. I have planned to test more deeply how ASYM_PACKING works with EAS when i will have finished others on going activity. >