3 ms·
And it's what's being done now on mainframes too. What was lacking in the commodity processor space was hardware support for mature hypervisors that stay out o
by monocasa 12y ago
And it's what's being done now on mainframes too. What was lacking in the commodity processor space was hardware support for mature hypervisors that stay out of the data plane (IBM got this right pretty close to the first try). We're almost there, but there's still some work IMO.
- pjmlp 12y agoOS/400 with kernel JIT, quite a nice design.
- monocasa 12y agoActually OS/400 isn't quite what I'm talking about (despite being really cool!). {AS|OS}/400 is more like a cross between a minicomputer and all of those promises of a Java OS we were given in the 90's. I'm talking more about the mainframe level stuff, like z/TPF on the software side and adding address space tags to the channels on the hardware side. Basically that last one is a better implementation of an IO/MMU where a device knows that it's probably running under a hypervisor, can get requests directly from multiple VMs without the hypervisor's intervention, and the VMs requests are implicitly tagged with the address space of the VM so it's still memory safe. ie. a VM can't request DMA from a device that would be outside of it's allocated space, but it can still directly ask the device for DMA without involving the hypervisor directly, and the device can service multiple VMs (that last bit is what isn't really present with current IO/MMUs).
- pjmlp 12y agoI used to start backup jobs on a AS/400 during a summer internship back in 1994, just logged in and started the respective job. Only more than a decade later I bothered to delve into how it actually works. I was quite surprised to discover that Java, .NET, Android, Windows Phone concepts were already successfully implemented in the marked in such systems, so many years before. And that the majority of developers out there are unaware of them. Thanks for the z/TPF overview.