RT-Smart Open Source Micro-kernel Operating System

Home > On-Demand Archives > Theatre Talks >

RT-Smart Open Source Micro-kernel Operating System

Bernard Xiong - Watch Now - EOC 2022 - Duration: 21:44

Bernard Xiong

Abstract Test Your Knowledge Questions & Comments (1)

There's a growing demand for embedded operating systems, and it's best when the one you build upon is open source. The RT-Thread project's R&D team has spent three years of research and intensive development to arrive at the project's latest offering: RT-Thread Smart. It is a microkernel operating system aimed primarily at midrange to high-end processors such as RISC-V or Arm Cortex-A that with a memory management unit (MMU) and provides a competitive and POSIX-based software platform for all industries in the embedded space.

Topics include:

What is Micro-Kernel Operating System?
What's RT-Smart and Who needs RT-Smart?
Application Scenarios

1 / 3

Please log in or create an account to test your knowledge and see the answers.

What is the primary architectural choice Bernard Xiong highlights as defining RT-Thread Smart compared with a traditional monolithic RTOS?

A It keeps all system services in kernel space to minimize context switches and maximize performance.

B It separates kernel space and user space so system services run in user space, providing isolation and on-demand loading.

C It removes the kernel entirely and runs all code as bare-metal tasks for deterministic timing.

D It only supports single-core processors to simplify scheduling and guarantee real-time behavior.

E It requires all applications to be statically linked into a single image to simplify deployment.

What is the role of LWP (Light-Weight Process) in RT-Thread Smart as Bernard describes it?

A A GUI framework for building user interfaces with JavaScript and hardware acceleration.

B A device driver framework that forces all drivers to run in kernel space for speed.

C A component that provides process management, virtual memory/MMU support, and IPC between processes and the kernel.

D A compatibility layer that translates POSIX calls into proprietary kernel APIs but without virtual memory.

E A debugger agent that replaces GDB on the device for remote debugging.

How does RT-Thread Smart maintain strong real-time performance while supporting user-space POSIX services, according to the presentation?

A By moving all interrupt handling to user-space services to reduce kernel complexity.

B By using a very small kernel (around 500 KB) that retains RT-Thread's hard real-time features and handles interrupts with very low latency, while non-critical services run isolated in user space.

C By disabling the MMU at runtime to avoid virtual memory overhead and ensure deterministic timing.

D By requiring all applications to avoid threads and only use event-driven callbacks to reduce scheduling overhead.

E By supporting only basic POSIX I/O but not POSIX threads, which simplifies scheduling for real-time tasks.

M↓ MARKDOWN HELP

italics	surround text with asterisks
bold	surround text with two asterisks
hyperlink	[hyperlink](https://example.com) or just a bare URL
code	surround text with `backticks`
~~strikethrough~~	surround text with ~~two tilde characters~~
quote	prefix with >

Upvotes Newest Oldest

leandropg

Score: 0 | 4 years ago | no reply

Hi Bernard... Thanks for the talk... I don't understand the difference between RT-Thread and RT-Thread Smart? ... And what is a good resource to start to use RT-Thread initially with microcontrollers ARM Cortex-M? Thanks

Login

Topic(s) Covered

About Bernard Xiong