> I was asking for requirements, not a design proposal. In order to make a > design you need a requirements specification.
Here's what I came up with ... not a fully baked list, but should allow for some useful discussion on whether any of these are not really needed, or if there is a glaring hole that misses some use case: 1) Able to measure using all supported events (currently L3 occupancy, Total B/W, Local B/W) 2) Measure per thread 3) Including kernel threads 4) Put multiple threads into a single measurement group (forced by h/w shortage of RMIDs, but probably good to have anyway) 5) New threads created inherit measurement group from parent 6) Report separate results per domain (L3) 7) Must be able to measure based on existing resctrl CAT group 8) Can get measurements for subsets of tasks in a CAT group (to find the guys hogging the resources) 9) Measure per logical CPU (pick active RMID in same precedence for task/cpu as CAT picks CLOSID) 10) Put multiple CPUs into a group Nice to have: 1) Readout using "perf(1)" [subset of modes that make sense ... tying monitoring to resctrl file system will make most command line usage of perf(1) close to impossible. -Tony
