From owner-freebsd-current Sat Dec 7 17:10:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA19287 for current-outgoing; Sat, 7 Dec 1996 17:10:15 -0800 (PST) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA19280 for ; Sat, 7 Dec 1996 17:10:08 -0800 (PST) Received: from campa.panke.de (anonymous216.ppp.cs.tu-berlin.de [130.149.17.216]) by mail.cs.tu-berlin.de (8.6.13/8.6.12) with ESMTP id BAA20012; Sun, 8 Dec 1996 01:58:08 +0100 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id XAA00532; Sat, 7 Dec 1996 23:52:07 +0100 Date: Sat, 7 Dec 1996 23:52:07 +0100 From: Wolfram Schneider Message-Id: <199612072252.XAA00532@campa.panke.de> To: Poul-Henning Kamp Cc: Paulo Menezes , current@freebsd.org Subject: Re: mount_mfs In-Reply-To: <9955.849904535@critter.tfs.com> References: <9955.849904535@critter.tfs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: >>Ok, that is a solution! But what about mfs? I would not like to create a >>/var /etc /tmp for each of the machines. The real question is can mfs be >>used to create an empty ram-disk rw for /tmp? > >Well, mfs has no real speed advantage over any "real" filesystem since >we got the share VM/buffer code, so I generally avoid it. o no update(4) o no synchronus operation for creating/deleting files on disk >Remember that it isn't really a mfs but more like a >swap-partition-fs. It is a user process with contex switching and twice memory-to-memory copying. I think the word 'swap-partition-fs' is confusing. Mfs is a hack and not fully optimized for speed. See 'The Design and Implementation of the 4.4BSD Operating System', page 302-306. Wolfram