Date: Tue, 28 Apr 1998 10:11:11 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru> Cc: freebsd-fs@FreeBSD.ORG Subject: Re: VFS_SYNC(MNT_LAZY) Message-ID: <Pine.SV4.3.95.980428100649.21961A-100000@parkplace.cet.co.jp> In-Reply-To: <199804262043.AAA01087@tejblum.dnttm.rssi.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
If you haven't already you should read the Ganger & Patt papers and look at the softupdate code before you change anything that has to do with the syncer. When using softupdates, most of both synchronous and asynchronous writes become delayed writes and the syncer has an even more important role than before. Regards, Mike On Mon, 27 Apr 1998, Dmitrij Tejblum wrote: > This is called every 30 seconds by the syncer daemon for every > filesystem mounted read-write. > > Is there any good reason why every filesystem walk through list of all > vnodes, lock every vnode, check for waitfor == MNT_LAZY, and in this > case unlock and skip the vnode? > > I may replace this with goto around this loop, if nobody object. > > Then, ffs_sync does not "flush filesystem control information" with > MNT_LAZY. (That is, it doen't call VOP_FSYNC on the device). Should it > be same way in other filesystems? > > Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.95.980428100649.21961A-100000>