pkarashchenko edited a comment on pull request #5421: URL: https://github.com/apache/incubator-nuttx/pull/5421#issuecomment-1030709045
Yes. I got the idea. I'm familiar with time drift compensation techniques. But the case that I'm trying to fix is next. I'm having a system with 10ms systick. I want to organize a periodic event (for example send a message) with 30ms. To use this I'm arming periodic POSIX timer with 30ms period and have a task that is waiting for a signal published by POSIX timer. When signal is received, the message is sent. I assume that I can achieve better or less accuracy by setting task priority depending on the load of my system. But what I'm getting is a message with 40ms period not depending from task priority. I do not see any reasons for that, but that is how currently it works. So this is not a sleep() use case. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
