The paper [0] has some suggestions: an API (already existing and somewhat supported, called TRIM) to tell the disk that certain sectors are no longer in use, and atomic writes.
I guess I buy the claim that you're better off starting with a log-structured file system that will use new APIs to allocate and free chunks on the SSD, than to use a conventional file system that the SSD tries to optimize
I guess I buy the claim that you're better off starting with a log-structured file system that will use new APIs to allocate and free chunks on the SSD, than to use a conventional file system that the SSD tries to optimize
[0] https://www.usenix.org/system/files/conference/inflow14/infl...