Date: Mon, 24 Jul 2000 22:34:39 -0700 From: Kirk McKusick <mckusick@mckusick.com> To: Sheldon Hearn <sheldonh@uunet.co.za> Cc: hackers@FreeBSD.ORG Subject: Re: Where is the syncer kernel process implemented? Message-ID: <200007250534.WAA12006@beastie.mckusick.com> In-Reply-To: Your message of "Fri, 14 Jul 2000 14:51:13 %2B0200." <66769.963579073@axl.ops.uunet.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Sheldon Hearn <sheldonh@uunet.co.za> To: Alfred Perlstein <bright@wintelcom.net> Cc: hackers@FreeBSD.ORG, mckusick@FreeBSD.ORG Subject: Re: Where is the syncer kernel process implemented? In-reply-to: Your message of "Fri, 14 Jul 2000 05:38:58 MST." <20000714053858.L25571@fw.wintelcom.net> Date: Fri, 14 Jul 2000 14:51:13 +0200 Sender: Sheldon Hearn <sheldonh@axl.ops.uunet.co.za> On Fri, 14 Jul 2000 05:38:58 MST, Alfred Perlstein wrote: > /* > * System filesystem synchronizer daemon. > */ > void > sched_sync(void) It seems that the default sync delay, syncer_maxdelay, is no longer controllable via sysctl(8). Are there complex issues restricting the changing of this value in real time, or is it just not something people feel the need to change these days? Ciao, Sheldon. The value of syncer_maxdelay was never settable, as it is used to set the size of the array used to hold the timing events. It was formerly possible to set syncdelay, but that variable was replaced by three variables: 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. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200007250534.WAA12006>