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

danpetry notifications at github.com
Wed Mar 13 13:54:05 CET 2019


danpetry commented on this pull request.



> +modular as possible so unused features don't use up precious RAM or flash.
+Almost all features are provided as optional modules that have to be enabled
+explicitly at compile time.  A minimal RIOT configuration starts at around
+<2KiB flash and <1.5KiB RAM (including stack space for one thread and ISRs).
+
+Starting from there, the memory usage depends on the enabled features:
+
+- Non-networked control loop / sensing applications can fit on very small MCUs
+(eg., an Atmega328P with 2KiB RAM)
+- 6lowPAN networking currently starts at ~40KiB ROM and ~10KiB RAM
+- A 6lowpan enabled CoAP server requires ~60KiB ROM and ~15KiB RAM
+- a file system adds ~15 KiB ROM and ~2 KiB RAM
+
+#### Constrained networking
+
+RIOT should deliver best-in-class communication robustness and

the implication is that the robustness we *should* provide is at least as good as anyone else's. To generalise somewhat, there are a number of statements in this document which reflect aspirations, rather than the actual current state. Hence the frequent use of the word "should". I believe this is appropriate and gives us goals to aim towards, which is an implicit purpose of a guidance document. (Guiding our developers to keep us exactly where we are would seem to be unproductive.)
I would say the question is more like: is "robustness as good as anyone else's" a specific enough, and realistic, goal?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10162#discussion_r265110987
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190313/30c61539/attachment.html>


More information about the notifications mailing list