The wear levelling is done on the hardware side, so it doesn't really care about your partition/filesystem layout. What happens is that it keeps a table of "what the system thinks is block 1234 is currently on chip 3 offset 0010" and so on for every physical block, and then it's free to cycle which physical positions it uses. Imagine a rewrite: Instead of reusing the same block, it can take an unused block, write the new content there, update the "this is there"-table, and put the old block at the end of the queue of free ones. (I imagine it works better with TRIM support, since that lets the disk consider much more space as "free". )
It's the same translation map idea that is used for virtual memory.


Reply With Quote
