second test, same results, after a couple of hours, application web closed. and then everything was stuck.
third test, I reduced ramzsawp to half size and so far so good
edit:
insmod /lib/modules/current/ramzswap.ko disksize_kb=131072
wait a minute. does the n900 have 131mb free even after boot?
and then we momentarily swapoff the default partition,so 131mb have to be real ram. very risky operations.
insmod /lib/modules/current/ramzswap.ko disksize_kb=131072
wait a minute. does the n900 have 131mb free even after boot?
and then we momentarily swapoff the default partition,so 131mb have to be real ram. very risky operations.
are you sure with the above disksize we are not adding double that? is'nt the disksize the ram we are asking and not the target?
"disksize_kb is upper limit on uncompressed worth of data given device can hold. While, memlimit_kb is upper limit on compressed worth of data given device can hold.
I understand that specifying disksize_kb value as upper limit on uncompressed data size seems bit counter-intuitive but this is how it is... We need to present a "fixed-size" disk to kernel." (from the author of compcache).
Damn, freemangordon! First 720p, now compcache!
Maemo 5 is looking really good. And it's looking better now that we will soon not need to swap on the slow flash ever again.
