Linked by Thom Holwerda on Sun 14th Apr 2013 20:30 UTC
Hardware, Embedded Systems "In the past five years, flash memory has progressed from a promising accelerator, whose place in the data center was still uncertain, to an established enterprise component for storing performance-critical data. It's rise to prominence followed its proliferation in the consumer world and the volume economics that followed. With SSDs, flash arrived in a form optimized for compatibility - just replace a hard drive with an SSD for radically better performance. But the properties of the NAND flash memory used by SSDs differ significantly from those of the magnetic media in the hard drives they often displace. While SSDs have become more pervasive in a variety of uses, the industry has only just started to design storage systems that embrace the nuances of flash memory. As it escapes the confines of compatibility, significant improvements in performance, reliability, and cost are possible."
Permalink for comment 558570
To read all comments associated with this story, please click here.
RE[3]: Comment by TempleOS
by saso on Mon 15th Apr 2013 19:21 UTC in reply to "RE[2]: Comment by TempleOS"
Member since:

What you describe is already in place, it's called "suspend to RAM" (aka "sleep") and it's far from simple. There's tons of runtime state that needs to be stored and restored when a machine changes power states that isn't in main memory. Just a little food for thought:

* peripherals (graphics cards, displays, mice, scanners, etc.)
* timing circuits (programmable interrupt clocks, watchdogs, etc.)
* environmental dependencies (open network connections, security contexts, etc.)

All of these need to be gracefully taken care of and reinitialized, and if possible made to continue previously interrupted tasks. All of this is already handled by current OSes. And all of this is very, very messy and complicated.

Reply Parent Score: 5