On 30-Jul-00 Brian Fundakowski Feldman wrote:
> 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! /
> [EMAIL PROTECTED] `------------------------------'
>
>
Please forgive my late reply.. Just trying to catch up..
Given all of the above statements, why does BSD/OS (at least on 4.0 and 4.1)
want to set up tmp as a Ramdisk? I don't even think there is a way around it
during the install.
Nicole
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
[EMAIL PROTECTED] |\ __ /| (`\ http://www.unixgirl.com/
[EMAIL PROTECTED] | o_o |__ ) ) http://www.dangermouse.org/
// \\
---------------------------(((---(((-----------------------------------------
-- Powered by Coka-Cola and FreeBSD --
-- Strong enough for a man - But made for a Woman --
-- OWNED? MS: Who's Been In/Virused Your Computer Today? --
-------------------------------------------------------------------------------
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
