5 ms·
Windows Internals is the canonical resource. (I bet you would enjoy the concurrency and I/O sections from The Be Book and The Design and Implementation of the
by Q6T46nT668w6i3m 11y ago
Windows Internals is the canonical resource.
(I bet you would enjoy the concurrency and I/O sections from The Be Book and The Design and Implementation of the FreeBSD Operating System too.)
- twoodfin 11y agoIs The Be Book available in PDF or ebook format anywhere?
- mattds 11y agoI believe you can find something about BeOS here: https://www.haiku-os.org/legacy-docs/bebook/index.html https://www.haiku-os.org/legacy-docs/bebook/index.html
- nickpsecurity 11y agoSpecifically as described here: https://users.cs.jmu.edu/abzugcx/Public/Student-Produced-Term-Projects/Operating-Systems-2003-FALL/BeOS-by-Nicole-Chung-Brian-Hoffman-Robert-Robinson-AJ-Schuster-2003-Fall.doc https://users.cs.jmu.edu/abzugcx/Public/Student-Produced-Ter... The benaphores were a brilliant idea. Plus, the general threading approach that avoided issues with direct, pointer manipulation. Add microkernels, memory protection, and threading all the way down for quite a unique kernel with incredible performance on old hardware. I'd be curious what a vanilla port of BeOS kernel on modern, multicore hardware would do vs a typical OS in fair benchmarks. We'd also include a little note that only one does it relatively safely. ;)