From owner-freebsd-hackers Tue Jul 25 0:59:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id 2F6A137BAB0 for ; Tue, 25 Jul 2000 00:59:09 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.15 #1) id 13Gzc9-0000Lt-00; Tue, 25 Jul 2000 09:58:57 +0200 From: Sheldon Hearn To: Kirk McKusick Cc: hackers@FreeBSD.ORG Subject: Re: Where is the syncer kernel process implemented? In-reply-to: Your message of "Mon, 24 Jul 2000 22:34:39 MST." <200007250534.WAA12006@beastie.mckusick.com> Date: Tue, 25 Jul 2000 09:58:57 +0200 Message-ID: <1356.964511937@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jul 2000 22:34:39 MST, Kirk McKusick wrote: > time_t filedelay = 30; /* time to delay syncing files */ > time_t dirdelay = 29; /* time to delay syncing directories */ > time_t metadelay = 28; /* time to delay syncing metadata */ > > Each of these variables is individually setable. These are maximum offsets from the current queue offset (syncer_delayno) at which new vnode entries may be inserted. That means they can be changed arbitrarily without fear of "orphaned" slots, right? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message