John, >>> - if (priority > 0) >>> + if (priority > 1 && !sameprio) >>> priority--; >> Unless I'm missing something really obvious, shouldn't this one state: >> if (priority > 0 && !sameprio) >> priority--; >> Or else 1 will be the lowest priority. It's a similar situation in >> "[PATCH 1/2] add-smp-option-to-ptsematest.patch" as well. > Carsten, is it useful to have SCHED_OTHER for this test? Don't think so. These tests (svsematest, ptsematest etc.) are intended as additional tests to cyclictest. I used them to make sure that the implementations of the various semaphore mechanisms (that mostly boil down to the same kernel code) do not introduce additional latencies. It may be sufficient to have cyclictest equipped with the numerous (and exotic) options. Another plan was to add a plugin slot to cyclictest, since probably more than 90% of the code of the various test programs is identical. A plugin version of cyclictest would provide all the various runtime and scheduler options, the stop clocks and the test framework. The actual test plugin could be specified as a command line argument. The plugin interface would need to connect the start and stop code of a particular test to cyclictest. But this was just a plan... Carsten. -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
