Date: Mon, 8 Jun 1998 23:35:51 -0400 From: "Allen Smith" <easmith@beatrice.rutgers.edu> To: Eivind Eklund <eivind@yes.no> Cc: hackers@FreeBSD.ORG Subject: Re: Newbie 3 questions. Message-ID: <9806082335.ZM20914@beatrice.rutgers.edu> In-Reply-To: Eivind Eklund <eivind@yes.no> "Re: Newbie 3 questions." (Jun 8, 2:33pm) References: <199806080349.UAA29145@grebe.Stanford.EDU> <199806080414.XAA01195@dyson.iquest.net> <19980608143347.59513@follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 8, 2:33pm, Eivind Eklund (possibly) wrote: > ... and (as John well knows) it can be tuned to run an async policy > similar to the one in Linux. Which policy you run is a tradeoff > between the security of synchronous metadata updates (you get the > guarantees that you don't get data crossing over from file to file > during crashes, that directories don't get totally screwed up, etc) vs > speed in massive manipulation of the filesystem (large amounts of > renames, creation of lots of small files, etc). The default policy is > the safest of these. Is async necessary/desirable for an MFS, or is it automatic? From the 4.4BSD book, I know that the 4.4BSD MFS is built just like a FFS, only using pageable memory space instead of filesystem space. Thanks, -Allen P.S. If it isn't automatically async, I might see if I can patch things so that it is. Somebody else doing this would be preferable, however. 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?9806082335.ZM20914>