--AYCDT44HuZYhsDxA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 13, 2005 at 01:25:56PM +1100, matthew green wrote:
>   =20
>    IMO removing tmpfs auto-sizing feature is a way to go.
>    ie. mandate -s option of mount_tmpfs and trust it.
>=20
> i want tmpfs to resize based on how much ram i have, or swap, or
> some cmobo, by default.  having to change static configuration
> parameters when i simply add memory is a concept that should be
> dead in this millennium...

Plus, -s is the wrong way around.  That's an upper limit on the size
of files you can store in tmpfs. The problem here is the reverse - not
having enough free space reported in tmpfs because filecache (or some
other better use of the memory) gobbled it all in the meantime.

I'm guessing this problem is only really evident on machines without,
or with relatively small, swap space.  Otherwise, free pages in swap
would be 'available' to tmpfs, and when allocated would push out file
cache pages.

--
Dan.

--AYCDT44HuZYhsDxA
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFDdsJ6EAVxvV4N66cRApQnAKCkjp24C4ucBODSh7ewqOFtmbD7pACgsQxq
bQk2PbNAVvIEXmEB9MLsJBk=
=2VhU
-----END PGP SIGNATURE-----

--AYCDT44HuZYhsDxA--