For example: The datasheet for ATtiny2313 (as do most Atmel AVR datasheets) states:
128 Bytes In-System Programmable EEPROM Endurance: 100,000 Write/Erase Cycles
Imagine a program only requires two bytes to store some configuration, the other 126 bytes are effectively wasted. What concerns me is that regular updates of the two configuration bytes may wear out the device's EEPROM and render it useless. The whole device would become unreliable, because at a certain moment you just can't keep track of which bytes in EEPROM are unreliable.
Is there a smart way to do wear leveling on a microcontroller's EEPROM when you effectively use only one or two bytes out of available 128?