Hi John, On 28 March 2018 14:29, John Ogness wrote: > On 2018-03-28, Phil Edworthy <phil.edworthy@xxxxxxxxxxx> wrote: > > I found that cyclictest results vary from one run to another. > > > > [...] > > > > Is it common knowledge that cyclictest results vary so much from one > > run to another? Any ideas how to mitigate this? > > It would be helpful if you provided the command arguments you use for your > tests. Particularly important options to consider: > > -a / --affinity > -m / --mlockall > -n / --nanosleep > -t / --threads > --secaligned > > and of course giving it an appropriate realtime priority: > > -p / --priority Sure: cyclictest -m -n -Sp99 -i200 -h300 -M -D 10h Thanks Phil -- 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
