Honestly, I have no idea. It *shouldn't* be a concern, due to speed of RAM, but if kernel is wasting too much "thinking" about where to include pages (= is searching for biggest free continuous blocks gap), who knows... It depends on kernel implementation of writing to swap. On Fremantle, we *shouldn't* get hit by swap fragmentation problem, although, we are. freemangordon suspects wrong implementation of managing writing to swap (after whole swap space is used sequentially), and is investigating possible ways to fix it...

so, maybe we will live to a day, when ereswap won't be needed anymore

/Estel