InitRech 2015/2016, sujet 25 : Différence entre versions
(→Summary) |
(→Summary) |
||
| Ligne 7 : | Ligne 7 : | ||
RiotOS is based on 3 key design aspects: | RiotOS is based on 3 key design aspects: | ||
| − | + | * The kernel has a microkernel architecture inherited from FireKernel, for the multi-threading with standard API. | |
| − | + | *He has C support and Riot adds a C++ support and a TCP/IP networks stack, making a developer-friendly OS with high reliability. Furthermore, Riot is able to create as many threads are needed by the developers. The number of threads is only limited by the available memory and stack size for each thread. | |
| − | + | * The scheduler uses a fixed-sized circular linked list of threads.The MCUs provide multiple compare registers, providing a way to have a constant runtime of the timer operations. The scheduler works without any periodic events for energy-efficiency. | |
These aspects of Riot OS gives him an efficient scheduling and a low memory footprint. He is open source, useful for the community and developing plugins and applications for free. He requires less than 5kB of ROM and 1.5 kB of RAM, can run on devices with 16-bit microcontrollers to 32-bit processors. | These aspects of Riot OS gives him an efficient scheduling and a low memory footprint. He is open source, useful for the community and developing plugins and applications for free. He requires less than 5kB of ROM and 1.5 kB of RAM, can run on devices with 16-bit microcontrollers to 32-bit processors. | ||
Version du 19 juin 2016 à 11:10
Summary
Riot OS is an OS for the Internet of Things (IoT). We can define the IoT like the network of all the physical devices (including phones, vehicles, sensors, etc.). There should be 50 billion devices in the IoT by 2020. The devices in the IoT can have very few resources, so Riot OS wants to be available for a maximum of devices and exploiting all the resources. An OS for IoT also needs to fulfil the requirements of cyber-physical systems, reliability, real-time behaviour and adaptive communication stack.
One of the main concern about the IoT is to have an OS that can run on all the available devices. Furthermore, there is a tradeoff between being developer-friendly (like Linux) and energy-efficient (like TinyOS and Contiki).
RiotOS is based on 3 key design aspects:
- The kernel has a microkernel architecture inherited from FireKernel, for the multi-threading with standard API.
- He has C support and Riot adds a C++ support and a TCP/IP networks stack, making a developer-friendly OS with high reliability. Furthermore, Riot is able to create as many threads are needed by the developers. The number of threads is only limited by the available memory and stack size for each thread.
- The scheduler uses a fixed-sized circular linked list of threads.The MCUs provide multiple compare registers, providing a way to have a constant runtime of the timer operations. The scheduler works without any periodic events for energy-efficiency.
These aspects of Riot OS gives him an efficient scheduling and a low memory footprint. He is open source, useful for the community and developing plugins and applications for free. He requires less than 5kB of ROM and 1.5 kB of RAM, can run on devices with 16-bit microcontrollers to 32-bit processors.
Main Contribution
The main contribution of this article is to summarise the differences between the differents OS for the IoT and see that Riot OS keep the best of each. The table explains what are the pros and cons of each OS and which architecture or functionality give them these strengths or weaknesses.
This article explains the needs for an OS specific to the devices of the IoT and wants to show the dominance of Riot OS on the IoT OS market. All the aspects of this OS are better than the others.
The article also explains the architecture and design aspects of the OS, and why it makes it better.
