Linear Address Spaces: Unsafe at any speed
About Flat vs. Object stores<p>I wrote this piece, frustrated by, what looks to me, like the entire semiconductor industry is only exploring one single computer storage organization, despite the fact that recent inventions like flash practically begs for innovation.<p>For instance few people realize that the Flash Adaptation Layer in the SSD devices means that we literally run two filesystems on top of each other, because nobody has seriously tried to get rid of the &quot;a disk is an array of individually rewritable sectors&quot; despite this literally being untrue both for modern disks and in particular for Flash based storage.<p>Similarly, the &quot;flat physical&#x2F;flat virtual&quot; MMU model is a relic from the days of IBM 360 and VAX 11&#x2F;780 and utterly inefficient and unsuitable for what we do in userland these days.<p>As Robert has shown with CHERI, there is plenty of space to innovate without breaking existing code.<p>And yes, C can be object oriented, all you have to do is keep your hands from the primitives which are necessary to access hardware directly.<p>Architectually GPU&#x27;s are a superoptimized distraction, like the vector-units on Cray and Convex computers were 40-50 years ago, but those too can function in a non-flat address-space.<p>But even C in OO-mode, and C++, Go, Rust, PHP and for that matter LISP and SmallTalk, would benefit from an HW&#x2F;MMU architecture which focused on delivering fast object service, rather than flat address-spaces which software must then convert into objects.<p>But to innovate, we must first realize that we are currently stuck in a box, and dare to look outside it.