| Javier González | a4bd217 | 2017-04-15 20:55:50 +0200 | [diff] [blame] | 1 | pblk: Physical Block Device Target |
| 2 | ================================== |
| 3 | |
| 4 | pblk implements a fully associative, host-based FTL that exposes a traditional |
| 5 | block I/O interface. Its primary responsibilities are: |
| 6 | |
| 7 | - Map logical addresses onto physical addresses (4KB granularity) in a |
| 8 | logical-to-physical (L2P) table. |
| 9 | - Maintain the integrity and consistency of the L2P table as well as its |
| 10 | recovery from normal tear down and power outage. |
| 11 | - Deal with controller- and media-specific constrains. |
| 12 | - Handle I/O errors. |
| 13 | - Implement garbage collection. |
| 14 | - Maintain consistency across the I/O stack during synchronization points. |
| 15 | |
| 16 | For more information please refer to: |
| 17 | |
| 18 | http://lightnvm.io |
| 19 | |
| 20 | which maintains updated FAQs, manual pages, technical documentation, tools, |
| 21 | contacts, etc. |