Well, sounds all good, but how does the controller know this? There MIGHT be come blocks of reserved memory used to indicate which blocks have been used and which ones haven't but that doesn't mean that filling the memory with 1's will reset it. What the OP is saying is that by filling the drive with 0xFF bytes (all 1's) it will reset the controller in some way so that it doesn't have to read the block before doing the write because it will know that block is empty. This is normal operation and the controllers have this functionality built into them thus to the end user, and even the OS, they don't see this operation. If you're writing to a block of memory but are not filling the block, the controller has to read the entire block, replace the components that you are writing, and then write the entire, modified, block back to the memory. This is because the SSD memory operates in blocks, all accesses either read a block, or write a block of memory. This takes time, but has to be performed regardless of the data in the RAM. ![]() On a write an SSD device has to do a read modify write operation if the write does not fill the entire block of RAM.
0 Comments
Leave a Reply. |