From owner-freebsd-current Sun Aug 22 11:25:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 0647B150AE for ; Sun, 22 Aug 1999 11:25:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA04303; Sun, 22 Aug 1999 20:23:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Sync(8) doesn't have any effect on softupdates-enabled filesystem In-reply-to: Your message of "Sun, 22 Aug 1999 10:58:10 PDT." <199908221758.KAA80382@apollo.backplane.com> Date: Sun, 22 Aug 1999 20:23:33 +0200 Message-ID: <4301.935346213@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908221758.KAA80382@apollo.backplane.com>, Matthew Dillon writes: >:> structures used internally by softupdates are not condusive to doing a >:> hard-sync. >: >:I gues sync needs to set a flag which makes the sync'er go through all >:buckets with no delay and then wake the sync'ing process afterwards... >: >:-- >:Poul-Henning Kamp FreeBSD coreteam member > > It won't help. What needs to happen is for the VOP_FSYNC in ffs to > figure out buffer<->buffer dependancies But the buffer to buffer dependencies are already recorded in the sequence on the "sync-wheel" which the syncer daemon runs through, isn't it ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message