How nguyenhuy0206/os_assignment works
Project type and purpose
• This is a C-based operating-system simulator (OS_Assignment) used for academic OS coursework. It reads input job traces (process descriptions, scheduling scenarios, paging scenarios), runs through kernel‐module simulations (CPU, loader, scheduler, memory management, paging, timer, queues), and writes out behavior logs to an output directory.
File structure
• Top-level directories:
• / – public headers defining interfaces for each OS module (cpu, loader, mem, mm, sched, timer, queue, paging).
• src/ – implementation (.c) files for each module.
• input/ – test workloads (process lists, scheduling scenarios, paging scenarios).
• output/ – simulator’s logging results.
• obj/ – compiled object files (intermediate build artifacts).
• os/ – built executable lives here.
• Makefile orchestrates build: compiles src/*.c into obj/*.o, then links into the “os” binary.
Detail
• Don’t over-simplify: show sub-components inside Memory (physical allocator vs. VM/paging).
• Every module defined in include/ and src/.
• Clearly how test inputs map to simulation paths and how outputs are generated.