Re: [PATCH]sched: Isochronous class v2 for unprivileged soft rtscheduling

[Jack O'Quin]

Jack O'Quin <joq@xxxxxx> writes:

> Will post the correct numbers shortly.  Sorry for the screw-up.

Here they are...

  http://www.joq.us/jack/benchmarks/sched-isoprio
  http://www.joq.us/jack/benchmarks/sched-isoprio+compile

I moved the previous runs to the sched-fifo* directories where they
belong.  For convenience, I moved all the summary data logs here...

  http://www.joq.us/jack/benchmarks/.SUMMARY

Unfortunately, these corrected tests do not compare favorably with the
earlier sched-fifo runs (mistaken or otherwise).  I wanted to believe
the problem was just a matter of priorities, but evidently it is not.

In fact, for this test the priority scheduler does not really help at
all (though I believe it will for other things).  The max delay
numbers are still all over the place...

...benchmarks/sched-iso...
Delay Maximum . . . . . . . . : 21410   usecs
Delay Maximum . . . . . . . . : 36830   usecs
Delay Maximum . . . . . . . . :  4062   usecs
...benchmarks/sched-iso+compile...
Delay Maximum . . . . . . . . : 98909   usecs
Delay Maximum . . . . . . . . : 39414   usecs
Delay Maximum . . . . . . . . : 40294   usecs
Delay Maximum . . . . . . . . : 217192   usecs
Delay Maximum . . . . . . . . : 156989   usecs
...benchmarks/sched-isoprio...
Delay Maximum . . . . . . . . : 37071   usecs
Delay Maximum . . . . . . . . : 98193   usecs
Delay Maximum . . . . . . . . : 36935   usecs
...benchmarks/sched-isoprio+compile...
Delay Maximum . . . . . . . . : 59662   usecs
Delay Maximum . . . . . . . . : 151624   usecs
Delay Maximum . . . . . . . . : 39250   usecs

I'll try building a SCHED_RR version of JACK.  I still don't think it
will make any difference.  But my intuition isn't working very well
right now, so I need more data.

I still wonder if some coding error might occasionally be letting a
lower priority process continue running after an interrupt when it
ought to be preempted.
-- 
  joq
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/