18c2ecf20Sopenharmony_cipblk: Physical Block Device Target 28c2ecf20Sopenharmony_ci================================== 38c2ecf20Sopenharmony_ci 48c2ecf20Sopenharmony_cipblk implements a fully associative, host-based FTL that exposes a traditional 58c2ecf20Sopenharmony_ciblock I/O interface. Its primary responsibilities are: 68c2ecf20Sopenharmony_ci 78c2ecf20Sopenharmony_ci - Map logical addresses onto physical addresses (4KB granularity) in a 88c2ecf20Sopenharmony_ci logical-to-physical (L2P) table. 98c2ecf20Sopenharmony_ci - Maintain the integrity and consistency of the L2P table as well as its 108c2ecf20Sopenharmony_ci recovery from normal tear down and power outage. 118c2ecf20Sopenharmony_ci - Deal with controller- and media-specific constrains. 128c2ecf20Sopenharmony_ci - Handle I/O errors. 138c2ecf20Sopenharmony_ci - Implement garbage collection. 148c2ecf20Sopenharmony_ci - Maintain consistency across the I/O stack during synchronization points. 158c2ecf20Sopenharmony_ci 168c2ecf20Sopenharmony_ciFor more information please refer to: 178c2ecf20Sopenharmony_ci 188c2ecf20Sopenharmony_ci http://lightnvm.io 198c2ecf20Sopenharmony_ci 208c2ecf20Sopenharmony_ciwhich maintains updated FAQs, manual pages, technical documentation, tools, 218c2ecf20Sopenharmony_cicontacts, etc. 22