How mikaku/fiwix works
Main Structural Components
a. User Space (External Interface)
• As the topmost layer
• ELF binary support
• System calls interface
b. Kernel Space (Core Components)
In the following logical groups:
Process Management
• Scheduler (sched.c)
• Process control (process.c)
• Signal handling (signal.c)
Memory Management
• Components from /mm/
• Virtual memory management
• Page allocation
• Memory mapping
File System Layer
• VFS abstraction
• Supported filesystems:
• EXT2
• Minix (v1/v2)
• ISO9660
• PROCFS
• PIPEFS
• SOCKFS
Device Drivers
• In categories:
• Block devices (ATA, ATAPI, Floppy)
• Character devices (Console, Keyboard, Serial)
• PCI devices
• Video/Graphics
IPC Mechanisms
• Unix sockets
• System V IPC components
• Pipes
Use the following visual elements:
• Rectangles: Major subsystems
• Rounded rectangles: Interfaces
• Hexagons: Hardware interfaces
• Blue: Core kernel components
• Green: File systems
• Yellow: Device drivers
• Gray: Hardware layer
• Purple: IPC mechanisms
• Double lines: Data flow
Key Relationships to Highlight
• System call interface connecting user space to kernel
• VFS abstraction layer connecting to specific filesystems
• Device driver hierarchy
• Memory management interaction with process management
• IPC mechanisms crossing between processes
Additional Elements
• Version information (current: MIT License, Copyright 2018-2024)
• POSIX compliance points
Technical Details
• Virtual memory split options (3GB/1GB and 2GB/2GB)
• Supported hardware specifications
• Key kernel features (non-preemptive, 32-bit protected mode)
• Multiboot specification compliance
Remember to emphasize:
• The UNIX-like architecture
• POSIX compatibility
• The educational/hobby nature of the project
• Core kernel features
• Hardware support limitations
This will provide a comprehensive view of the Fiwix kernel architecture while maintaining clarity and usefulness for both educational and development purposes.