Date: Wed, 26 Apr 1995 17:09:28 +1000 From: Bruce Evans <bde@zeta.org.au> To: hackers@FreeBSD.org, imb@asstdc.scgt.oz.au Subject: Re: async mounts .. bogus ? Message-ID: <199504260709.RAA09681@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>I was experimenting with the async mount attribute in an effort to speed up >this machine's handling of news but observed two problems .. >asstdc:~ vmstat -m >Memory statistics by bucket size >Size In Use Free Requests HighWater Couldfree >... > 8K 38 7 162 5 97 <---- where from ??? :-) In FreeBSD-1.x, "Couldfree" meant "missed opportunities to free". It apparently still means this - on my freefall there are now 450792 1K and 861 8K buffers in the "Couldfree" column. I hope freefall doesn't have 450MB of leaked memory. I hope it has 450MB of unleaked memory :-). >Memory usage type by bucket size This has some anomalies too. Lots of buckets have type `temp'. Shouldn't `temp' be only for short-lived allocations? > .. ultimately, I came back into the room to find that it had rebooted >itself in order to dispense with my alteration :-(. >Is "mount -o async" still bogus in 950412-SNAP (which is what I'm running) ? I think "-o osync" is still close to a no-op. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504260709.RAA09681>