If you've been following this blog, you've probably noticed a lot of discussion and analysis around eMMC. We've written about the reasons we are so excited about eMMC, but also why the Write Amplification issues caused by eMMC parts are a problem that needs more attention by the industry.
The challenge - making ext4 just as reliable as Datalight's Reliance Nitro file system, within limitations of the POSIX specification. Unlike most real world embedded designs, performance and media lifetime are not a consideration for this exercise.
We're constantly on the lookout for ways to help our customers boost performance and improve power efficiency, and often our inspiration comes by way of the conversations we have with them. Recently, several of these discussions highlighted user scenarios where the complexity of the application would benefit from an enhancement to the classic Dynamic Transaction Point™ technology found in our Reliance Nitro file system.
In conversations with the embedded OEMs we work with, a common issue affects almost every manufacturer - the cost of diagnosing and fixing causes of field failure. This impacts time-to-market and pulls resources from development for field diagnostics and post-mortem analysis. This issue is especially relevant due to the following reasons:
Last week's Flash Memory Summit did not disappoint. As one of the early sponsors of the conference, it was awe-inspiring to stand in the middle of the exhibit hall and see how the show has grown, in both number of booths and attendees.
Wikipedia describes Write Amplification as "an undesirable phenomenon associated with Flash memory and solid-state drives (SSDs) where the actual amount of physical information written is a multiple of logical amount intended to be written," and offers this formula to calculate it: