Ok I have gained a bit more information on this now. Apparently, the
filter is there, for HPC loads to exclude scheduler activity itself from
the scheduler?
Filtering all the processes for this, seems completely unessecary though.
Depending on what resolution these filters run at, you have 50 filters
running at resolution X, only to do that, with 50 processes. Why not just
replace that with a simple, on off, say cpu usage = 0 for the first 1 ms.
Scheduler activity probably doesn`t last longer than that, atleast with
preempt on. And with a filter you will have 10ms activity indication after
the last input. That should just be truncated, and after 1ms things should
just work on peak values. (not average).
From thinking about how this filter would improve anything, that seems
like the better way to do anything like that.
Peace Be With You.