News for hackers. Stuff that matters.
Re:SSDs: A gift and a curse by wtallis on Tuesday June 02, 2015 @01:21PM (#9647381)
Having the flash translation layer on the drive itself is the only practical way for the drive to be usable by multiple operating systems. Almost everyone who uses a SSD wants it to be accessible to at least two operating systems (UEFI, and whatever OS resides on the SSD). Doing the FTL on the host system would basically relegate the SSD to being just a cache device.
Re:SSDs: A gift and a curse by kabdib on Wednesday June 03, 2015 @12:18AM (#9650558)
Yup. I looked at this while doing design work for a certain highly visible gaming product. You want the responsibility for block leveling and transactional goop close to the device, where the firmware can know stuff about device geometry and other nasty bits that affect reliability.

Putting that stuff in the OS puts you back to, oh, the same wicked stuff that people had to deal with for MFM hard drives (remember cylinder, head and sector counts? Only probably ten times more complicated).

A block level abstraction is fine, as long as the abstraction can make some transactional guarantees.

Re:SSDs: A gift and a curse by zokier on Tuesday June 02, 2015 @01:33PM (#9647487)
We have these things called standards which allow nice things like interoperability. Besides, you do not need the entire drive to be accessible from UEFI, it is enough that you can load a small bootloader which contains the drivers to handle the disk. Thirdly, UEFI has extensible right in the name, shouldn't be too hard for OSes to throw a disk driver blob into UEFI.
Re:SSDs: A gift and a curse by bduerst on Tuesday June 02, 2015 @03:48PM (#9648468)
Doesn't that require partitioning the disk? That doesn't seem like an OOB solution.
Re:SSDs: A gift and a curse by wtallis on Tuesday June 02, 2015 @04:10PM (#9648596)
It's not the requirement to partition the drive that kills the idea. Setting aside the first small chunk of the drive for the firmware to read is how it's always been done. The problem is that this would require the partitioning to be done below the wear leveling layer, which reduces the effectiveness of the wear leveling slightly and means you can only change your bootloader settings a thousand times before the drive is dead.
Re:SSDs: A gift and a curse by Dylan16807 on Wednesday June 03, 2015 @01:59AM (#9650808)
That's not really what kills it. You can use a small ring buffer to boost that to 100 thousand, and/or use the flash in a more reliable way there (like SLC or devoting 2/3 of the bits to ECC).
Re:SSDs: A gift and a curse by pgeorgi on Tuesday June 02, 2015 @04:52PM (#9648881)
sadly with NAND even reads contribute to wear.