How damiramirez/go-so-2024 works
Main Components
• Kernel: Acts as the central coordinator and contains submodules for process management (PCB management), scheduling algorithms (FIFO, Round Robin, Virtual Round Robin), longterm/shortterm planning, resource management, and blocking.
• CPU: Responsible for low-level instruction handling. Its internal structure includes components for fetching, decoding/dispatching, executing instructions, and TLB management.
• Memory (Memoria): Manages memory operations. It contains modules to handle memory functions, utilities, and supports configurations linked to deadlock and TLB setups.
• I/O Subsystem (Entradasalida): Manages device interactions (e.g., generic I/O, keyboard, monitor, file system I/O, and specialized scenarios like Salvation’s Edge). It provides API servers for handling requests.
• Auxiliary Modules and Utilities: This includes shared utilities such as logging, configuration management, request handling, and serialization, which support all major components.
Interactions
• That configuration files (found in each module’s “config” directory) are responsible for defining operation modes (e.g., scheduling algorithms, TLB policies) that are injected into each module.
• That there are API layers in each major module (shown in the “api” directories) that allow for networked or inter-process communication (e.g., the Kernel’s API with handlers for planning, process management, and I/O operations).
Architectural Patterns and Design Principles
• Modular Structure: Each core system (kernel, CPU, memory, and I/O) is isolated in its own directory with an internal breakdown (e.g., API servers, handlers, internal logic, global configuration).
• Configurability: The heavy use of external JSON configuration files demonstrates a design for high customizability (e.g., switching scheduling policies or memory management strategies).
• Testing and Process Simulation: The “run” scripts and “procesos” directory indicate that the system is built for rigorous testing by simulating processes and scenarios like deadlock, planning, and FS interactions.
Essential Architectural Elements
• Detail every internal module that is key to the simulation (e.g., CPU’s “fetch”, “dispatch”, “execute” pipelines; Kernel’s “block”, “longterm”, “shortterm” modules).
• External integrations are represented, such as the API endpoints each module exposes (i.e., the “handlers” directories).