is TMPFS still highly experimental?

[Xin LI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 10/03/11 11:36, Attila Nagy wrote:
> On 10/03/2011 07:14 PM, Xin LI wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>> 
>> Hi, Attila,
>> 
>> On 10/03/11 04:29, Attila Nagy wrote:
>>> For me, the bug is still here: $ uname -a FreeBSD b 8.2-STABLE 
>>> FreeBSD 8.2-STABLE #5: Wed Sep 14 15:01:25 CEST 2011 
>>> root at buildervm:/data/usr/obj/data/usr/src/sys/BOOTCLNT  amd64 $
>>> df -h /tmp Filesystem    Size    Used   Avail Capacity  Mounted
>>> on tmpfs           0B      0B      0B   100%    /tmp
>>> 
>>> I have no swap configured. The machine has 64 GB RAM. 
>>> vm.kmem_size=60G; vfs.zfs.arc_max=55G; vfs.zfs.arc_min=20G
>> This sounds like a configuration issue.  Running without swap is
>> not recommended anyways.
> I guess it depends on the workload. In general, you are possibly
> right, but if you need predictable response times and you can
> tolerate dying processes, swapping may not be the right thing to
> do.

Well, in that case one will have to tolerate tmpfs have no page to
allocate (note that it does need to reserve some pages for system use)
at this point.  Currently it's working like a credit line -- use it
here and you can't use it elsewhere, e.g. if user process used it then
tmpfs can't use it...

I think the only solution we can have here is to teach tmpfs about
"dedicated reserve for tmpfs" so it pre-allocate a few pages that can
not be reused elsewhere?  E.g. create a budget that make this part of
memory "tmpfs fund" :)

Cheers,
- -- 
Xin LI <delphij at delphij.net>	https://www.delphij.net/
FreeBSD - The Power to Serve!		Live free or die
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBCAAGBQJOigIyAAoJEATO+BI/yjfBVPwH/2iXNPkTmgzN0pxoB/Xhrw96
TYeJkDLevVuRTVi82VDuCqrUtJeMsf0rSLdNS201AZc6+7e/rPzBWVaKSKowH9BP
vY67TnbSMgG6UEnVrVZ29JMy7RHoWDapqEd5+kYxVOwi+jX8tzh+HZsqgWUjOe+F
mSvv0lcvEgGyeFkPD0HoJni73noXKgumd6Eben7hN+CAwYkOWlWLYKZiHTyFqlWK
To41Bg9je3FUgL95RJpoMvvO4GVRWaU95UyarMuM1ulh7WKe8/JW8QEcDaVTtABJ
QIlAROPmkeagqjkHWaprAz46sJhFczShSr6DX2unhsGGCPq83eUWkOip8GDdQw4=
=l3Ji
-----END PGP SIGNATURE-----