On 01/05/2017 11:58 PM, Slava Dubeyko wrote: > Next point is read disturbance. If BER of physical page/block achieves some threshold then > we need to move data from one page/block into another one. What subsystem will be > responsible for this activity? The drive-managed case expects that device's GC will manage > read disturbance issue. But what's about host-aware or host-managed case? If the host side > hasn't information about BER then the host's software is unable to manage this issue. Finally, > it sounds that we will have GC subsystem as on file system side as on device side. As a result, > it means possible unpredictable performance degradation and decreasing device lifetime. > Let's imagine that host-aware case could be unaware about read disturbance management. > But how host-managed case can manage this issue? The OCSSD interface uses a couple of methods: 1) Piggy back soft ECC errors onto the completion entry. Tells the host that a block properly should be refreshed when appropriate. 2) Use an asynchronous interface, e.g., NVMe get log page. Report blocks through this interface that has been read disturbed. This may be coupled with the various processes running on the SSD. 3) (That Ted suggested). Expose a "reset" bit in the Report Zones command to let the host know which blocks should be reset. If the plumbing for 2) is not available, or the information has been lost on the host side, this method can be used to "resync". > > Bad block management... So, drive-managed and host-aware cases should be completely unaware > about bad blocks. But what's about host-managed case? If a device will hide bad blocks from > the host then it means mapping table presence, access to logical pages/blocks and so on. If the host > hasn't access to the bad block management then it's not host-managed model. And it sounds as > completely unmanageable situation for the host-managed model. Because if the host has access > to bad block management (but how?) then we have really simple model. Otherwise, the host > has access to logical pages/blocks only and device should have internal GC. As a result, > it means possible unpredictable performance degradation and decreasing device lifetime because > of competition of GC on device side and GC on the host side. Agree. depending on the use-case, one may expose a "perfect" interface to the host, or one may expose an interface where media errors may be reported to the host. The former case are great for consumer units, where I/O predictability isn't critical, and similarly if I/O predictability is critical, the media errors can be reported, and the host may deal with them appropriately. -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
