Red Bear OS
00b4c141b2
Adds the full second half of the CORE-C12 fix: - scheme_pool::SchemePool: a per-scheme worker pool that takes closures and dispatches SchemeWork items to dedicated worker threads via mpsc channels. Each worker calls the closure under Arc<Mutex<Smolnetd>> so the smolnetd state is held briefly per event but the workers run in parallel. The pool also tracks per-scheme statistics (events_processed, bytes_processed, pending, events_dropped) via atomics for observability. - scheme_pool_init::register_all: a helper that registers the standard netstack scheme set (ip, udp, tcp, icmp) against a SchemePool, mapping each scheme to its on_X_scheme_event method on the smolnetd. - corec12_integration: the main loop integration layer. The new run_corec12_main_loop function drains a ReaderPool (per-NIC packet reads), routes the bytes into the smolnetd via per-scheme submit, then calls on_network_scheme_event on the smolnetd. End-to-end test pipeline mirrors the real flow with a Mock-style smolnetd. - worker_pool::OwnedFd: a small adapter that wraps a raw file descriptor in std::fs::File via dup. The reader pool now accepts any Read + Send + 'static input, so both std::fs::File and the OwnedFd bridge work. The pool stays generic. Phase 7 has the corresponding proptest + reader-pool unit tests for parallel I/O (4 worker threads complete in <200ms even though each has 50ms-sleep payload). The smolnetd currently uses Rc<RefCell<...>> internally which is not Send, so a small refactor of Smolnetd's state model (Arc<Mutex<Smolnetd>> for cross-thread access) is the next step. The scheme_pool_init closure captures Arc<Mutex<Smolnetd>> and the worker takes the lock briefly per event; once Smolnetd's internal state uses std::sync::Mutex instead of RefCell, the worker threads can take the lock without Send issues. This is a separate refactor that lives as a follow-up patch.
Base
Repository containing various system daemons, that are considered fundamental for the OS.
You can see what each component does in the following list:
- audiod : Daemon used to process the sound drivers audio
- bootstrap : First code that the kernel executes, responsible for spawning the init daemon
- daemon : Redox daemon library
- drivers
- init : Daemon used to start most system components and programs
- initfs : Filesystem with the necessary system components to run RedoxFS
- ipcd : Daemon used for inter-process communication
- logd : Daemon used to log system components and daemons
- netstack : Daemon used for networking
- ptyd : Daemon used for pseudo-terminal
- ramfs : RAM filesystem
- randd : Daemon used for random number generation
- zerod : Daemon used to discard all writes and fill read buffers with zero
How To Contribute
To learn how to contribute you need to read the following document:
If you want to contribute to drivers read its README
Development
To learn how to do development with these system components inside the Redox build system you need to read the Build System and Coding and Building pages.
How To Build
It is recommended to build this system component via the Redox build system, you can learn how to do it on the Building Redox page.
To build and test outside the build system, install redoxer then use check.sh script to build or test:
./check.sh- Check build for x86_64./check.sh --arch=ARCH- Check build for specific ARCH (aarch64,i586,riscv64gc)./check.sh --all- Check build for all ARCH./check.sh --test- Check the base system boots up on x86_64
You can also use make install to inspect the content on ./sysroot, or make test-gui to test booting with orbital interactively.