/explore
|
You are here 
|
venam.net | ||
| | | | |
mohit.athwani.net
|
|
| | | | | [AI summary] An educational article explains the UNIX fork() system call, detailing how parent and child processes function, how to differentiate them via PID, and provides C++ code examples for process creation and management. | |
| | | | |
cpu.land
|
|
| | | | | Curious exactly what happens when you run a program on your computer? Learn how multiprocessing works, what system calls really are, how computers manage memory with hardware interrupts, and how Linux loads executables. | |
| | | | |
thorstenball.com
|
|
| | | | | [AI summary] The article explains how Unicorn, a web server, leverages Unix system calls and concepts like fork, pipe, and signal handling to efficiently manage web requests. It highlights features such as hot reloading, zero downtime deployments, and worker process scaling using signals. The author emphasizes that these capabilities are not magic but a result of understanding and utilizing Unix's low-level mechanisms. The article also discusses the importance of knowing system-level details for debugging, architectural decisions, and deeper understanding of how software operates on the underlying system. | |
| | | | |
blog.stephenmarz.com
|
|
| | | [AI summary] The text provides an in-depth explanation of how C programs are compiled into assembly and machine code, focusing on various aspects such as data types, memory sections, control structures, and the role of the compiler in making decisions about load/store operations and shifts. It covers topics like data type conversions, padding in structures, global variables, and branch instructions for conditions and loops. The text also mentions the importance of understanding assembly for learning how compilers work and the use of tools like objdump for analyzing compiled code. | ||
