6 ms·
Windows Kernel Architecture Internals (2010) [pdf]
- srean 11y agoI have always heard that the windows kernel is actually pretty well designed. In particular the way it handles concurrency and asynchronous I/O. Unfortunately I have not found (euphemism for: I have been lazy) an easily consumable description of its differences from the Unix, Linux APIs supporting concurrency and asynchrony features, in what ways are they better, with some code examples thrown in that illustrate the differences If anyone would be so kind to humor me with such a comparison or pointer...
- Q6T46nT668w6i3m 11y agoWindows 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. ;)
- ksk 11y agoWell you have to be careful with what you're comparing. It would be rather unfair to compare the original UNIX design with a modern design like NT. UNIX did not have async I/O. It even blocked syscalls in its original design. I think Linux added async I/O quite recently (2.6?). I'm not really a kernel dev, but I have had to work on systems level stuff quite often on both OSs and from what I've seen NT has a much more richer I/O model. The I/O class/device/filter/driver model of NT makes writing driver code less of a chore IMHO. Also async I/O is supported on almost all I/O devices. I believe its only network and disk on Linux.
- nickpsecurity 11y agoUNIX intentionally deviated from monolithic systems that had many useful features because they couldn't run on their hardware. Then, they kept that even when hardware got better with some added back in band-aid on ways and some others cleanly. Windows NT's design came from experience and strategies of OpenVMS's designer. No wonder that a cleaner, monolithic design came out of it. Took them a while to get the reliability near their ancestor, though. Haha. Meanwhile, QNX and Minix 3 took a more UNIX philosophy approach than UNIX by decomposing the whole thing into communicating components. QNX did it fast and ultra-reliable where Minix 3 is at least reliable. Easier to update due to architecture, even live updates. They each did this with little manpower and resources compared to what went into UNIX's. My direct comparison for UNIX is with them. It shows UNIX architecture is fundamentally flawed in terms of flexibility, reliability, security, determinism, and ease of maintenance. I'd compare Windows kernel with other monoliths on servers and desktops. Usability and stability are better than most that are still around with other attributes hit and miss (or comparable). UNIX desktops have gotten much better than before but still too many WTF moments. And more dependency hell than I used to deal with on Windows. (sighs)
- richardwhiuk 11y agoDependency hell has very little to do with kernel design - it's entirely a user mode problem. Neither Linux or Windows NT in the modern iterations are true monolithic kernels - e.g. on Linux FUSE allows filesystems in user space, loadable and unloadable kernel modules, Windows has a User mode drivers framework which is increasingly used post Vista. Neither QNX or Minix are as feature full as Linux or Windows NT - almost all development on Linux and Windows is in driver development, not core kernel work (e.g. scheduler, IO system, memory manager). Windows NT remains a more modern kernel (in terms of internal consistent object model, basic kernel primitives) than either BSD or Linux, but whether it's absolutely better is a harder argument. In general the argument regarding micro/monolithic kernels is old hat in practice we can make extra-ordinarily reliable monolithic kernels, while we can also avoid a lot of the pain associated with microkernels - e.g. minimising context switch time. The reliability, security, flexibility argument is largely made redundant by man-power dropped into modern kernels - better use Linux because although it's theoretically inferior it has 1000s of days of development thrown at it. Kernel development also appears to be transitioning to using safety in compilers to improve reliability, but that's been a research topic for decades - the answer to 'can we build a sufficiently smart compiler' has been 'maybe' for a long time - though LLVM and Rust's compiler show a way forwards.
- marcocampos 11y agoFor more about this, have a look at "Windows Internals" (6th edition is the latest, I believe) by Mark Russinovich, David Solomon and Alex Ionescu. It's an awesome book.
- tinco 11y agoAnyone know if there's work being done on a 7th edition of Windows Internals? I read Inside Windows 2000, which was totally awesome, but not super much changed on the architectural level between 2000 and Windows 7 (which is covered in the 6th edition), at least not to my untrained eye. Windows 8 and 10 might have some radically new stuff, just judging from the range of devices they target, and their efforts on speeding it up on slower hardware (reversing the trend of the bloating Windows versions up to Vista). Now I've not really used Windows much in the past 10 years. I switched to OSX and then to Ubuntu (when the desktop experience became more bearable, and the license issues with OSX more important to me). But reading about the NT kernel feels like reading about how a kernel should be designed. It really is that much cleaner in my opinion than anything I ever read on OSX or Linux. If they ever did open source it, I'd certainly join a subculture of before-it-got-hip Windows kernel lovers with XMonad as a window manager ;)
- dr_zoidberg 11y agoWindows Internals 7th Edition Book 1 is available already[0], and there will be 2 more books[1]. Russinovich and Solomon have stepped down a while ago, according to that forum thread, but the new book lists them as authors because Catlin and Hanrahan worked over the already existing stuff. [0] http://www.amazon.com/Windows-Internals-Book-User-Edition/dp/0735684189 http://www.amazon.com/Windows-Internals-Book-User-Edition/dp... [1] http://forum.sysinternals.com/when-is-the-7th-edition-book-for-win-8-coming-out_topic29288_post142573.html#142573 http://forum.sysinternals.com/when-is-the-7th-edition-book-f...
- deleted 11y ago[deleted]
- nikital 11y agoIf you're into NT kernel internals, I recommend an excellent book "What Makes It Page?". It describes the VMM in way too much detail (in a good way). It's a great combination of theory and practice - it describes concepts and then shows them on the live kernel. For example, the author introduces the concept of cache coloring and then he shows in WinDbg the actual variable on the process data structure where the color is stored. http://www.amazon.com/What-Makes-It-Page-Windows/dp/1479114294 http://www.amazon.com/What-Makes-It-Page-Windows/dp/14791142...
- trentnelson 11y agoPhenomenal book, highly recommended.