From owner-freebsd-hackers Tue Jun 30 03:14:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18288 for freebsd-hackers-outgoing; Tue, 30 Jun 1998 03:14:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18231; Tue, 30 Jun 1998 03:14:34 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id MAA13587; Tue, 30 Jun 1998 12:11:48 +0200 (CEST) To: Peter Wemm cc: "Paul T. Root" , rminnich@Sarnoff.COM (Ron G. Minnich), hackers@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: looking for ram file system (NOT MFS) In-reply-to: Your message of "Tue, 30 Jun 1998 06:11:28 +0800." <199806292211.GAA03588@spinner.netplex.com.au> Date: Tue, 30 Jun 1998 12:11:47 +0200 Message-ID: <13585.899201507@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199806292211.GAA03588@spinner.netplex.com.au>, Peter Wemm writes: >"Paul T. Root" wrote: >> In a previous message, Ron G. Minnich said: >> > I'm looking for something like a ram file system for some work i'm doing. >> > It needs to support ram-based lookup, mkdir, rmdir, etc. It needs to be >> > BSD or GPL copyright, and run under current. Any pointers appreciated. >> >> mfs > >Recheck the subject line: "looking for ram file system (NOT MFS)" > ^^^^^^^^^ >I believe Poul-Henning Kamp was working on a mallocfs at some point.. > >MFS is bad in that it doesn't allocate and release swap. It'd be seriously >great to have something that could allocate and free pageable memory as >files were written and deleted. MFS never releases swap space once the >mount_mfs process faults in an anon page. Doing it seperately from UFS >would be a good start since it wouldn't be wasting time emulating a disk >structure. Actually doing it separately from UFS would be a waste of time, but that is a different issue. the mallocfs I wrote used the kernel malloc and was consequently limited to 20Mbyte and non-pageable. A "vmfs" is on my wishlist too... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message