Messages in this thread | | | Date | Mon, 6 Aug 2018 12:02:13 +0100 | From | Quentin Perret <> | Subject | Re: [PATCH v5 09/14] sched: Add over-utilization/tipping point indicator |
| |
On Monday 06 Aug 2018 at 12:45:44 (+0200), Vincent Guittot wrote: > On Mon, 6 Aug 2018 at 11:43, Quentin Perret <quentin.perret@arm.com> wrote: > I would have preferred to have a full power policy for all task when > EAS is in used by default and then see if there is any performance > problem instead of letting some UC unclear but that's a personal > opinion.
Understood. I'd say let's keep things simple for now unless there is a consensus that this is must-have form the start.
> so IMO, the minimum is to add a comment in the code that describes > this behavior for fork tasks so people will understand why EAS puts > newly created task on not "EAS friendly" cpus when they will look at > the code trying to understand the behavior
Agreed, that really needs to be documented. I'll add a comment somewhere in v6.
Thanks, Quentin
| |