1*4882a593Smuzhiyunpblk: Physical Block Device Target 2*4882a593Smuzhiyun================================== 3*4882a593Smuzhiyun 4*4882a593Smuzhiyunpblk implements a fully associative, host-based FTL that exposes a traditional 5*4882a593Smuzhiyunblock I/O interface. Its primary responsibilities are: 6*4882a593Smuzhiyun 7*4882a593Smuzhiyun - Map logical addresses onto physical addresses (4KB granularity) in a 8*4882a593Smuzhiyun logical-to-physical (L2P) table. 9*4882a593Smuzhiyun - Maintain the integrity and consistency of the L2P table as well as its 10*4882a593Smuzhiyun recovery from normal tear down and power outage. 11*4882a593Smuzhiyun - Deal with controller- and media-specific constrains. 12*4882a593Smuzhiyun - Handle I/O errors. 13*4882a593Smuzhiyun - Implement garbage collection. 14*4882a593Smuzhiyun - Maintain consistency across the I/O stack during synchronization points. 15*4882a593Smuzhiyun 16*4882a593SmuzhiyunFor more information please refer to: 17*4882a593Smuzhiyun 18*4882a593Smuzhiyun http://lightnvm.io 19*4882a593Smuzhiyun 20*4882a593Smuzhiyunwhich maintains updated FAQs, manual pages, technical documentation, tools, 21*4882a593Smuzhiyuncontacts, etc. 22