-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2013-05-06 at 21:50 -0400, Anton Aylward wrote:
Or NOT as the case may be.
First, a tmpfs is mapped to memory in a way that slightly more efficient than a disk based FS. Yes, disk based FSs are mapped to memory, buffers, for reading writing inodes and super-blocks as well as shuffling the B-trees and indexes and more. By comparison a tmps is incredibly light weight.
Secondly, Linux uses a demand paged virtual memory so you're never going to run out of memory, for whatever value of 'never' applies. And it does apply here. If that memory is needed by a process it can be paged out to swap.
If, for example, gimp needs to store a temporary file of 4 GB in /tmp, in my computer that means it will swap (I have 8GiB ram, and swap is used already). Swap being used that lot means that most of the system applications will be impacted. On the other hand, if /tmp is disk, only gimp is impacted. Or... I read comments the other day of some one using k3b. It turned out that dvd images were going to /tmp - again, huge usage. Worse: many people nowdays do not even create swap! They think that computers with 8 GiB are big enough. No, thanks, I do not want /tmp in RAM. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGIa/8ACgkQtTMYHG2NR9V1lACffuNoGKR5lyNjLRZR8Jf5NpIb 20sAnj4JyjYP4hk9n8WWkekCwp2fycYu =rGFQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org