View Single Post
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#88
Originally Posted by peterleinchen View Post
But to minize wear to the maximum:
what about not disabling flip location, but enabling flop location with higher priority?
This will lead to flip still used (only read of old data) and all new swap on flop. Or/and vice versa. This way we do not have the need to move the currently used swap data.

Maybe I do not increase, but create second swap ....
But, without moving swap data and physically turning one down, it doesn't get un-fragmented, so when swap 2 also hit the limit, changing priority to higher for swap 1 won't help in fighting fragmentation...

So, it works only, until both swaps hit the limit. But, maybe after giving higher priority for swap 2, we could wait some time, and then quickly disable and re-enable (with still lower priority) swap 1, so it will be ready for taking higher priority again? Due to sitting with lower priority for some time, it should contain low amount of data for read, anyway.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following 3 Users Say Thank You to Estel For This Useful Post: