Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

DAxelrod (4649)

  (email not shown publicly)

I'm interested in hard problems.

Recently, I've started thinking a lot about what CP6AN might look like.

Class::MOP and the Perl 6 Metamodel make me more excited than I'd like to admit.

Also expect occasional wordy technology-related rantings.

Journal of DAxelrod (4649)

Tuesday July 24, 2007
08:26 PM

MMU Announced [News from an Alternate Timeline]

[ #33877 ]

In a press release today, Imtel announced a new processor hardware component, called a Memory Management Unit.

"The MMU will supplement our existing VX-t technology in offloading virtualization overhead to the processor itself," said Imtel's Bob Brooke.

While it has been possible for years to give applications the illusion of controlling the computer's entire memory address space, the in-software techniques employed by hypervisors have always meant taking a performance hit, especially when it was necessary to swap memory to disk. The MMU allows applications to send instructions directly to the processor, negating the need for a software-based address translation layer.

But Imtel claims the biggest benefit will be hardware-enforced "memory protection", ensuring that different applications cannot read or modify each others' memory. Brooke went on to claim, "The containerization benefits of the MMU will provide unparalleled levels of security."

VMWear's Chan Du declined to comment specifically when asked if the MMU would be utilized by their upcoming hypervisor technology, the so-called Operating System Kernel. He would only say, "Operization Technology will provide many new ways to abstract hardware from individual applications, but it is our policy to not discuss features of unreleased products."

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.