The optimal policy in 1994 is : bind a high-bandwidth device (e.g., FDDI or UltraSCSI controller) to a dedicated CPU. That CPU runs the interrupt handler, the device driver's bottom half, and the user process that consumes the data. This "pipeline" design, seen in Sequent's DYNIX/ptx, can achieve 85% linear scaling for network I/O.
A subtle bug discovered in early 1994: the vfork() system call on 64-bit kernels did not properly restore the full 64-bit stack pointer after an exec, leading to silent corruption of high addresses. unix systems for modern architectures -1994- pdf
: The book details how to move beyond "Master/Slave" architectures (where only one CPU handles kernel tasks) to a truly symmetric model. This involves implementing mutual exclusion mechanisms like spinlocks , semaphores , and mutexes . The optimal policy in 1994 is : bind
Searched for: unix systems for modern architectures -1994- pdf A subtle bug discovered in early 1994: the
But what exactly is this document? Why has its PDF become a digital holy grail? And what arguments did it make that still echo in the Linux kernel and macOS (XNU) of today?