Re:Writing an OS in Rust: Hardware Interrupts
by DoritoChef on Monday October 22, 2018 @01:50PM
(#18276722)
From the historical point of view, this heavy decoupling is associated with microkernels which fell out of favor with the rise of the Linux kernel. I think in this day and age, modern programming languages could make building a microkernel that doesn't fall prey to the shortcomings of MINIX a possibility.
[ Parent
| on HN ]
Re:Writing an OS in Rust: Hardware Interrupts
by d33 on Monday October 22, 2018 @02:00PM
(#18276818)
Microkernels are IPC-heavy, right? What I rather imagine is having modules at source level, not kernel level. So the thing still compiles down to a monolith/hybrid, but modules are abstracted away and reusable.
Re:Writing an OS in Rust: Hardware Interrupts
by fooker on Monday October 22, 2018 @02:34PM
(#18277071)
Source level modules sound awesome.
Would need a high level language though.
Re:Writing an OS in Rust: Hardware Interrupts
by nicoburns on Monday October 22, 2018 @03:33PM
(#18277621)
Like Rust?
Re:Writing an OS in Rust: Hardware Interrupts
by fooker on Tuesday October 23, 2018 @04:14PM
(#18287010)
Maybe, I would personally go with C++.
Re:Writing an OS in Rust: Hardware Interrupts
by jacquesm on Monday October 22, 2018 @07:31PM
(#18279516)
The IPC overhead is very much manageable, microkernels tend to be a lot more responsive than monoliths and with paging for message passing the overhead is reduced even further.
Re:Writing an OS in Rust: Hardware Interrupts
by badosu on Monday October 22, 2018 @02:18PM
(#18276951)
It would be interesting to see if modern multi-core cpus make the possible overhead of microkernels a non-issue today.
Re:Writing an OS in Rust: Hardware Interrupts
by jacquesm on Monday October 22, 2018 @07:32PM
(#18279526)
Microkernels are much easier to optimize for multi-core CPUs than monoliths. The ´kernel modules´ from a monolith run as user processes in a microkernel environment so they automatically benefit from more cores.