Red Bear OS
b3fd5cc682
Without explicit memory ordering, the Rust compiler is free to reorder loads of the device-written descriptor (status, length) relative to the writeback of the descriptor ownership flag. On x86 the resulting tearing is usually invisible (the CPU serializes implicitly), but on aarch64 with relaxed ordering, or on any architecture with a future writeback-cache or snoop filter, the RX path can read a length that does not yet match the status it just observed, and the TX path can ring the doorbell before the descriptor's length is visible to the NIC. Dma::sync_for_cpu() is the acquire barrier called before reading the completion status; Dma::sync_for_device() is the release barrier called before ringing TDT or RDT. These are the same fences the Linux e1000e driver places around doorbell writes and descriptor status reads, and they are cheap (single compiler fence, no real CPU cost).
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.