I recently started to study how nanosleep() behaves under 2.6.26.6-rt11 compiled in in FULL PREEMPT, uniprocessor mode.
I find that between 2.6.20-rt8 and this new kernel something has changed and nanosleep() is back to its old behavior
or sleeping for next higher number of msec rather than carefully following the "y=x" line.
I don't follow the RT world closely enough, but is this a regression or an expected change in behavior? The link below
show the results very clearly.
http://www.atl.external.lmco.com/projects/QoS/documents/nanosleep_1.png
Gautam
--
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
