How thomyluca/sistemas-operativos-1c2024 works
• Kernel
• Memoria (Memory)
• Cpu
• Entrada/Salida (I/O, handling devices like keyboard, monitor, file system, etc.)
The README details specific aspects such as multiple scheduling algorithms in the Kernel, a paging algorithm and TLB replacement strategies in Memoria, and a File System that can perform compaction. The file tree confirms that each module is self-contained with its own configuration files, headers, source code, and even testing scripts. There is also a shared “utils” directory that likely contains common functionalities for inter-module communications via sockets and other helper routines.
Functional Layers Within Each Module
• For Memoria, illustrate the memory management component, highlighting the paging algorithm and a separate TLB component (with FIFO and LRU replacement policies).
• For Cpu, mark the core execution logic and associated components (like instruction processing and communications interfaces).
• For Entrada/Salida, mark the various functionalities: keyboard, monitor, file systems (including aspects such as compaction), and other I/O components.
Relationships & Data Flows
• Bidirectional communication between Cpu and Memoria if such interactions exist (e.g., for fetching instructions or handling memory references).
• Similarly, show communication between Entrada/Salida and Kernel for I/O completions or interrupts.
• Optionally, show the shared “utils” layer as providing support to all these modules (e.g., through standardized communication protocols – the “sockets” related files suggest a network/socket-based architecture).
Architectural Patterns and Design Principles
• Separation of concerns across modules: each module’s own directory shows a clear division focused on its role.
• The use of configuration files (each module has a set of configs) indicates that the system is designed for flexibility in testing different scenarios (e.g., “Dead”, “Edge”, “Entrada”, “FS”, “Memo”, “Plani” configurations).
• Modular design that accommodates testing scripts separately (as seen in the “scripts” and “scripts-pruebas” directories), which is important for simulation testing.