On Sat, May 04, 2002 at 08:34:20PM +0200, Niels M?ller wrote: > Thanks for the explanation. I'm trying to understand what consequences > for performance can be expected. > > [EMAIL PROTECTED] (Thomas Bushnell, BSG) writes: > > > There are cases (as noted before) where the following sequence arises: > > > > write block A > > write block B > > write block A again > > > > and where the writes *must* occur in that sequence. (This often > > happens when block A contains two inodes, and block B must be written > > *after* the update of the first, and *before* the update of the > > second.) > > Does anybody have any idea how often this case occurs with typical > activities like compilation?
I think that for compilation we don't need to synchronize everything to be sure the filesystem the compilation happens on has an inconsistent. It doesn't really matter if you lose some objects files. Maybe it would be a nice thing to provide this as an option. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: jeroen@openprojects
msg04330/pgp00000.pgp
Description: PGP signature
