![]() |
Re: [DISCUSS] SDCard Swap Partition Methods..
Quote:
If you enable another flop location and disbable the flip location, all data will be moved from flip to flop. Enabling both swaps with same priority does not make sense. Nad enable them with different priority even less, as only higher priority will be used (except you reach 800MB swap usage, very unlikely). Only advantage I see is fully omitting swap space (wear) on eMMC. |
Re: [DISCUSS] SDCard Swap Partition Methods..
With ereswap you have 2 swap partitions, one on eMMC for backup and one on the SD card for main usage. When ereswap refresh the swap it put on the backup, put off the main and then backwards, put on the main, and put of the backup. These are 4 steps and 2 data movings, using backup swap for the transition.
If you would have 3 swap partitions you would have eMMC one for backup (only if you haven't the SD card or it's broken), and two in the SD card to alternate. When you want to refresh you just put on the swap2 and put off the swap1, and thats all. (Next swap refresh you will put off swap2 and put on swap1). Backup eMMC swap is never used (saving of damage his cells and damaging SD ones) and you only need 2 steps and one data moving. And 2 swap partitions share the damage to sd cells. I prefer the second method and I will try to modify ereswap to use it. I hope Estel likes the modification and integrates it in ereswap. Maybe could be make an option to use one or two swap partitions on SD Card, as user wants. |
Re: [DISCUSS] SDCard Swap Partition Methods..
I have N900 with swap on sd card partition. Swap on emmc is disabled.
And i have a problem with some osso applications. RSS, for example, after returning from microb, refreshing to main window, contacts refreshing to top of list after call. Both programs showing "<app name> - resuming" on the top. With emmc swap enabled glitch disappears. What to do? |
Re: [DISCUSS] SDCard Swap Partition Methods..
Quote:
I was not aware of second moving back, as I just have my SD swap as higher priority and only disf/enable it. So all data is moved once to eMMC and then read /forgotten from there and all new swap is located again on SD. Maybe not the best approach, but for me it works nicely. But two swaps on SD is also good approach to save eMMC wear. Maybe I add another swap file ... |
Re: [DISCUSS] SDCard Swap Partition Methods..
2 Attachment(s)
Quote:
I could do with a little help with the scripts I am making to complete the rest of my idea in post 67. Using some of the source of ereswap I have two scripts one for Swapping and one for Switching to Internal (to eject SD safely) but I can't work out how to get the current swaps and use them in the script. Bit new to the more involved scripting. If they work it would be possible to make a small app or be incorporated with ereswap somehow. |
Re: [DISCUSS] SDCard Swap Partition Methods..
Quote:
Sorry no time to look in your scripts, but cat /proc/swaps should give you info what swap is enabled... |
Re: [DISCUSS] SDCard Swap Partition Methods..
Quote:
Using Code:
cat /proc/swaps | awk '/dev/ {print $1}' |
Re: [DISCUSS] SDCard Swap Partition Methods..
You want output to store in a variable?
Normally I use version c Code:
cat /proc/swaps | awk '/dev/ {print $1}' |
Re: [DISCUSS] SDCard Swap Partition Methods..
@peterleinchen So when you put off SD swap, all data there is moved to eMMC swap, and afterwards when you put on SD swap, old data is on eMMC one and new data is writed to SD one.
I see a problem: eMMC will be used to have the old data after the refresh, and while your programs need that old data to be readed and loaded in RAM, you will be using some of the eMMC, so your mobile will be a bit slower (remember we use swap on SD for never using eMMC for swap and at the same time data from /home or /MyDocs (in eMMC too), soo we get less stress in eMMC). It's not a big problem, but well, would be better if you only use SD always. |
Re: [DISCUSS] SDCard Swap Partition Methods..
This toggles between SD/eMMC:
Code:
#!/bin/sh Code:
#!/bin/sh |
All times are GMT. The time now is 15:51. |
vBulletin® Version 3.8.8