On Tue, 7 Feb 2017, Stephane Eranian wrote:
>
> I think the design must ensure that the following usage models can be
> monitored:
> - the allocations in your CAT partitions
> - the allocations from a task (inclusive of children tasks)
> - the allocations from a group of tasks (inclusive of children tasks)
> - the allocations from a CPU
> - the allocations from a group of CPUs
What's missing here is:
- the allocations of a subset of users (tasks/groups/cpu(s)) of a
particular CAT partition
Looking at your requirement list, all requirements, except the first point,
have no relationship to CAT (at least not from your write up). Now the
obvious questions are:
- Does it make sense to ignore CAT relations in these sets?
- Does it make sense to monitor a task / group of tasks, where the tasks
belong to different CAT partitions?
- Does it make sense to monitor a CPU / group of CPUs as a whole
independent of which CAT partitions have been utilized during the
monitoring period?
I don't think it makes any sense, unless the resulting information is split
up into CAT partitions.
I'm happy to be educated on the value of making this CAT unaware, but so
far I only came up with results, which need a crystal ball to analyze them.
Thanks,
tglx
