-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-06-25 16:33, Anton Aylward wrote:
On 06/25/2014 09:35 AM, Carlos E. R. wrote:
As they say "YMMV" As I say "Context is everything"
Absolutely :-)
I would consider a tmpfs only if I could limit the RAM usage to something small, and force overflow to swap (or disk directory) early. That is, as a specialized disk cache for a special directory. An hybrid.
Years ago, Mike Tilson wrote a disk driver for V7 UNIX that kept the inode table in memory. Its since been outdated by better inode caching and by pathname caching and more. Perhaps what we need isn't so much a tmpfs as a better trade-off of the way memory is used. Perhaps a FUSE can do this, but it would need to be metricated. Many imaginative ideas don't hold up in the real world.
Years ago, in MsDOS, I had a third party disk cache that could be applied to a single partition, IIRC. That's basically it, dedicate a cache with fixed ram space to a single directory, in this case, "/tmp". Most accesses would work only in RAM, it would be persistent, and size would not be a problem. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOq6GoACgkQtTMYHG2NR9UuwQCfcbpCMCrxWHT6f+mfubjthndc KpEAnR+HruzqomR+AeTdk0UvDQst5gdo =xhz9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org