Search Results for "threads"

QP real-time event frameworks (RTEFs) provide lightweight, modern, event-driven architecture based on asynchronous Active Objects (Actors) and Hierarchical State Machines. The matching QM model-based design tool and other host-based tools complement the QP frameworks by supporting graphical modeling, code generation, software tracing, and unit testing for event-driven embedded software. Visit https://www.state-machine.com for more information. The QP RTEFs can run on bare-metal...

Simplest of possible ways to multithreading on the smallest microcontrollers. This project is demonstration the programming technique of the multithreading with polling the system state. Published code debugged and ready to use in your projects.

Pharos is a free open-source RTOS for secure, safe and real-time systems with the following characteristics: - Memory and enhanced time partitioning (TSP) - Native support for sporadic, periodic and aperiodic threads - Fixed-priority preemptive scheduler - Execution time protection (threads are prevented from executing for more time than they are configured to) - Small size (full image has ~100 to 300KiB text, ~30KiB data) - Hard real-time determinism - Fast critical sections - Prioritized nested interrupts - inter-partition communication with filters to protect unwanted access - Multicore support (RMP) - Supports ARM9, Cortex-A/R/M and Aarch64, RISC-V64 (64 bits) - The complete TestSuite (see below information) is run successfully for each platform in each release - Tested: more than 170 KLOC of requirement-based tests, executed for each board at each release - Up-to-date User Manual also available See our wiki page for more information.

This project is now in the research and development stage. It is intended for very small microcontrollers with a single processor and represent simple multithreading kernel what written by C language. Is planning create implementations for AVR8 and STM8, may be. Now it is suspended until better time.

...This only CPU then can access to this instance of FileSystem. The scheduler is based on the cooperative threading model, therefore due to this design, TORO can migrate threads between CPUs and send messages between threads without using any lock instruction. TORO is well suited for integrated system to run at high pace application servers like web servers.

This is a collection of libraries contained : Shared memory allocation, configuration script processor, containers (trees, lists, queues, stacks), file system abstraction, network library, timers/threads, Image library, Display libraries, and more.

Implementation of virtual threads for the XS-1. Currently a simple context switching implementation for the XMOS XS-1 architecture (Gn, Ln products). Allows a user to run low speed processes on a single thread using time sliced scheduling.

Multiple RX threads is a kernel module designed for improving networking performance for NAPI on multi-core system.

Trio extends the existing Linux scheduler to support proportional-share scheduling using a scheduling algorithm, called Distributed Weighted Round-Robin (DWRR). It allows users to control shares of CPU time for any thread or group of threads.

rtusd is a foundation set of real time enabled User Space Devices/Drivers designed to link to HRT high resolution Timer controlled POSIX threads and link re-factored Linux hdw drivers for 2.6.18+. rtusd propogates Linux RT to user space generically.

Lamp is a Unix-like environment that runs in a single process (via threads) on traditional Mac OS, including standard I/O, vfork/exec, a shell, perl, sockets, virtual fs with /dev and /proc, signals, and ptrace(). Runs on 68K/PPC, and on OS X as Carbon.

Tyros is a highly modular operating system aimed towards providing the unified interface between user-space applications and all types of system objects (i.e. threads, processes, users, computers, networks etc)

POSIX API for Win2K-XP. Mainly implemented in the driver. Included: write-on-copy fork, threads, mutexes, spins, condvars, rwlocks, signals ... Signals/cancelation interrupt all waitable syscalls, NT syscalls are automaticaly restarted.