[riot-notifications] [RIOT-OS/RIOT] doc/rdm: RFC - design goals (#10162)

danpetry notifications at github.com
Thu Jan 31 16:31:33 CET 2019

danpetry commented on this pull request.

> +Above the HAL, the only thing that modules should know about hardware is
+whether a required feature is there or not. If it isn't, the module should
+adapt accordingly, or not compile.
+## Real-time capabilities
+Different real-time guarantees are required for different use cases. Low
+frequency sensing needs only soft real-time support and can handle less timing
+accuracy so long as the timers support long timescales. High-frequency sensing
+and control applications need hard real-time guarantees and sub-millisecond
+timing accuracy.
+RIOT should deliver soft real-time performance by default, to cover the widest
+range of use cases. Programs with hard deadlines should be achievable with more
+expertise. It should provide timers which can competently handle the timescales
+of any application.

Thanks for the detailed explanation. It seems that to imply that no hard guarantees are ever achievable would be misleading, but also that giving hard real time guarantees is not the design focus of the kernel. (correct me if I'm wrong.)  

Would it be possible to nail down exactly what guarantees we want to intentionally design the system to give, in what situations?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190131/0ce1d9e9/attachment-0001.html>

More information about the notifications mailing list