From owner-cvs-all  Sat Jul  3 17:31:23 1999
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5115714C16; Sat,  3 Jul 1999 17:31:20 -0700 (PDT)
	(envelope-from mckusick@FreeBSD.org)
Received: (from mckusick@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id RAA84221;
	Sat, 3 Jul 1999 17:31:20 -0700 (PDT)
	(envelope-from mckusick@FreeBSD.org)
Message-Id: <199907040031.RAA84221@freefall.freebsd.org>
From: Kirk McKusick <mckusick@FreeBSD.org>
Date: Sat, 3 Jul 1999 17:31:20 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/kern vfs_cluster.c
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

mckusick    1999/07/03 17:31:20 PDT

  Modified files:
    sys/kern             vfs_cluster.c 
  Log:
  The vfs.write_behind sysctl and related code support has been added to
  allow changes to the filesystem's write_behind behavior.  By the
  default the filesystem aggressively issues write_behind's.  Three values
  may be specified for vfs.write_behind.  0 disables write_behind, 1 results
  in historical operation (agressive write_behind), and 2 is an experimental
  backed-off write_behind.  The values of 0 and 1 are recommended.  The value
  of 0 is recommended in conjuction with an increase in the number of
  NBUF's and the number of dirty buffers allowed (vfs.{lo,hi}dirtybuffers).
  Note that a value of 0 will radically increase the dirty buffer load on
  the system.  Future work on write_behind behavior will use values 2 and
  greater for testing purposes.
  
  Submitted by:	Matthew Dillon <dillon@apollo.backplane.com>
  Reviewed by:	Kirk McKusick <mckusick@mckusick.com>
  
  Revision  Changes    Path
  1.86      +40 -3     src/sys/kern/vfs_cluster.c



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message