Quote:
Originally Posted by knc1
On the other side of what? Reality?
Have you read the logs of what all the system does to verify the partitioning of the eMMC is 'as expected'?
Read the logs attached to the 'recover ... with fastboot' thread.
PS: only the /var/local sub-tree of /var is on its own partition.
The rest of the /var tree is already in RAM (specifically, the VFS cache blocks):
Code:
[root@kindle /var]# df .
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 32768 696 32072 2% /var
|
Sorry, English is not my mother language. what I meant with "other side" was:
-your proposal is using what we could loosely call "filesystem bytes" (eMMC) in order to have more virtual memory by using swap
-but the /var (
NOT /var/local) filesystem is using tmpfs and does exactly the contrary; it steals "virtual memory bytes" from RAM in order to give us more "filesystem bytes"
Hence my idea of just reducing the space occupied by the /var filesystem.Then it wouldn't use as many VFS blocks, more RAM is available for other things and swap is not needed.
It seems like only 3 files in /etc/upstart would need modification. Partitions are NOT touched.
.... but since I know little about internals of Linux memory management, maybe tmpfs is so "smart" that the following
Code:
[root@kindle /etc]# df /var
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 32768 1104 31664 3% /var
means only 1104K (as opposed to 32768) are really used. In which case my proposal is completely useless
BR,
Nix