2 ms·
It's clearly a combination of bad OS architecture, bad software architecture, and misalignment of hardware + software interests. We've seen improvements on the
by nickpsecurity 11y ago
It's clearly a combination of bad OS architecture, bad software architecture, and misalignment of hardware + software interests. We've seen improvements on the last two in different ways while OS improvements are hacks piled on hacks piled on original mess. There were attempts to improve performance with purpose-built designs: BeOS demo made desktop scream with performance; QNX smoked microkernels such as Mach; IX did this for dataplanes; mainframes' Channel I/O gives them insane throughput and utilization (90+%); Intel's i432, IBM's System/38, Burroughs B5500, Cavium's Octeon network SOC's, and recent Azul Systems Vega all accelerated critical functions with purpose-built hardware.
So, there's all kinds of ways to improve things at each layer. Many were done and are being done with vast improvements over the competition of the time period. Why do mainstream OS's not improve as mainstream hardware improves? Bad design, bad implementation, and strong desire for backward compatibility that makes fixes hard. Good news is there's a niche market and academic R&D that are always creating clean-slate stuff that does it better.
Admittedly, though, replacing a full OS isn't likely to happen as users reject anything without feature X, app Y, or benchmark Z. The thing is there's a lot of those things in an OS to the point that barrier of entry to building one is insanely high. Even Solaris 10, despite having a hell of a start, cost over $200 million to design, implement, and test. Best shortcut to that I've seen are the Rump kernels. That combined with the clean slate work means we might see a better thing happen incrementally over time.
- vezzy-fnord 11y agoAdmittedly, though, replacing a full OS isn't likely to happen as users reject anything without feature X, app Y, or benchmark Z. The thing is there's a lot of those things in an OS to the point that barrier of entry to building one is insanely high. Best shortcut to that I've seen are the Rump kernels. Well, not really. Rump kernels are a godsend shortcut (similar to DDE, but much more advanced) for device drivers, but Blub-loving users wanting their apps means you still need to roll a POSIX userland of some sort (the way GNU Hurd does it over Mach is quite interesting, it supports things like processes with multiple uids with all POSIX calls being RPC that delegates to object servers) or since we're talking about a mainstream improvement here, Darwin/XNU and maybe even Windows NT. No escape.
- nickpsecurity 11y agoThe L4 kernels have just been porting Linux, etc to user-mode to run the untrusted apps with calls to underlying API. Might be the best that can be done outside some kind of source to source translation with heuristics.
- adamnemecek 11y agoWhat were some of the main reasons that made QNX and BeOS fast? For BeOS, was it that the OS took advantage of asynchronous execution?
- nickpsecurity 11y agoanimats explained QNX's design and results very well on a HN thread. Google isn't giving me crap even when I type his exact words in. Only does that on HN for some reason. I pastebin'd my copy here: http://pastebin.com/2K119Wtj http://pastebin.com/2K119Wtj Far as BeOS, I found this word document where some people wrote up a summary of design decisions that boosted performance, reliability, and how easy it was to develop on vs eg POSIX. 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... Hope those help.
- adamnemecek 11y agoInteresting, thanks, I'll definitely check them out.