Date: Sun, 30 Jul 2000 16:28:54 -0400 (EDT) From: Michael Bacarella <mbac@nyct.net> To: Brian Fundakowski Feldman <green@FreeBSD.ORG> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: /tmp on a ramdisk? Message-ID: <Pine.BSF.4.21.0007301623320.44664-100000@bsd1.nyct.net> In-Reply-To: <Pine.BSF.4.21.0007301541480.36725-100000@green.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 30 Jul 2000, Brian Fundakowski Feldman wrote: > Yes, things are stored twice in memory: once in the buffer cache and > once in the MFS process. Yes, they are also copied multiple times. > MFS simply can't perform as well as you might expect. The malloc disk > device can because it simply creates a kernel-memory backing store. > The disadvantage here is that it's wired memory and can't get swapped > out like mount_mfs can. This is more out of curiousity than criticism; ..but why not just make a charecter device that corresponds to a chunk of VM and simply run newfs on that? You would still have a relatively proven filesystem (like FFS) and you also get the "benefits" of having it memory resident. Perhaps certain properties of FFS would be less than ideal for this, but you get the idea. Wouldn't this have the same problems as mfs but still avoid existing as a seperate filesystem (and thus, a seperate code base)? -MB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007301623320.44664-100000>