From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 16 03:45:21 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70E6E106567F; Tue, 16 Jun 2009 03:45:21 +0000 (UTC) (envelope-from ben@wanderview.com) Received: from mail.wanderview.com (mail.wanderview.com [66.92.166.102]) by mx1.freebsd.org (Postfix) with ESMTP id 150BE8FC19; Tue, 16 Jun 2009 03:45:20 +0000 (UTC) (envelope-from ben@wanderview.com) Received: from [10.76.10.146] ([10.76.10.146]) (authenticated bits=0) by mail.wanderview.com (8.14.3/8.14.3) with ESMTP id n5G3Co1m058549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 03:12:56 GMT (envelope-from ben@wanderview.com) Message-ID: <4A370DB2.8070403@wanderview.com> Date: Mon, 15 Jun 2009 23:12:50 -0400 From: Ben Kelly User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: Ivan Voras References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.44 () ALL_TRUSTED,AWL X-Scanned-By: MIMEDefang 2.64 on 10.76.20.1 X-Mailman-Approved-At: Tue, 16 Jun 2009 04:32:00 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: tmpfs experimental? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2009 03:45:21 -0000 Ivan Voras wrote: > Hi, > > Are there still known problems with tmpfs? > > I've been using it for a while in 7-STABLE and 8-CURRENT without > noticeable problems - not that there was ever serious load involved > (normal /tmp activity). I've just tried it and it survived a couple of > rounds of blogbench, even with virtual memory swapping. > > In other words, is there still reason for the "highly experimental > feature" warning? I get some slightly unexpected behavior when mount is run multiple times: ianto# mount | grep ' /tmp' tmpfs on /tmp (tmpfs, local) ianto# mount /tmp ianto# mount | grep ' /tmp' tmpfs on /tmp (tmpfs, local) tmpfs on /tmp (tmpfs, local) ianto# umount /tmp ianto# mount | grep ' /tmp' tmpfs on /tmp (tmpfs, local) ianto# It also occurred to me once that perhaps all tmpfs mounts should share the same UMA zones instead of a new zone for each mount, but thats a pretty minor issue: ianto# vmstat -z | grep TMPFS TMPFS dirent: 20, 0, 4, 165, 385, 0 TMPFS node: 136, 0, 5, 53, 386, 0 TMPFS dirent: 20, 0, 4, 165, 5541, 0 TMPFS node: 136, 0, 5, 53, 5542, 0 TMPFS dirent: 20, 0, 6, 163, 51031, 0 TMPFS node: 136, 0, 7, 80, 46927, 0 TMPFS dirent: 20, 0, 4, 165, 7542, 0 TMPFS node: 136, 0, 5, 53, 7543, 0 TMPFS dirent: 20, 0, 6, 163, 81644, 0 TMPFS node: 136, 0, 8, 79, 77463, 0 Overall tmpfs has been very stable for me as a mimedefang spool directory. Hope that helps. - Ben