Date: Sun, 30 Jul 2000 15:47:19 -0400 (EDT) From: Brian Fundakowski Feldman <green@FreeBSD.org> To: Adam <bsdx@looksharp.net> Cc: Doug Barton <DougB@gorean.org>, freebsd-hackers@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: /tmp on a ramdisk? Message-ID: <Pine.BSF.4.21.0007301541480.36725-100000@green.dyndns.org> In-Reply-To: <Pine.BSF.4.21.0007301531080.77768-100000@turtle.looksharp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
The issue is that mount_mfs is simply newfs with a catch: it constructs the new filesystem completely in memory and lives on as the storage for the mounted filesystem. If you view the processes on a system using MFS, you will notice that one of them is the original mount_mfs, having become a daemon. 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. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' 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.0007301541480.36725-100000>