Path: utzoo!attcan!uunet!samsung!munnari.oz.au!sirius.ucs.adelaide.edu.au!augean!sibyl!ian
From: ian@sibyl.eleceng.ua.OZ (Ian Dall)
Newsgroups: comp.arch
Subject: Re: Mixing paging and IO is inefficient (was Re:  Compiler partions)
Message-ID: <691@sibyl.eleceng.ua.OZ>
Date: 27 Jun 90 13:38:16 GMT
References: <499@garth.UUCP> <5660@titcce.cc.titech.ac.jp> <137770@sun.Eng.Sun.COM>
Reply-To: ian@sibyl.OZ (Ian Dall)
Organization: Engineering, Uni of Adelaide, Australia
Lines: 16

In article <137770@sun.Eng.Sun.COM> lm@sun.UUCP (Larry McVoy) writes:
}>My approach is not doing sync write on /tmp file system. By specifying
}>"delay" option with mount, most sync write to the file system is
}>replaced by delayed write.
}
}I'm really getting sick of this thread.  Those who understand file system
}semantics dismissed this idea as flawed from the start.  The synchronous
}nature of certain file system writes are *required* for file system
}reliability.

A really simple solution would be to make /tmp a seperate partition and turn
of sync writes. A mkfs (or newfs) takes of the order of the same time as
an fsck anyway. /tmp is usually cleared on a reboot so there is no problem.
-- 
Ian Dall     life (n). A sexually transmitted disease which afflicts
                       some people more severely than others.