From owner-freebsd-current  Fri Oct 29 12:47:52 1999
Delivered-To: freebsd-current@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP id 9E6F914BD8
	for <current@freebsd.org>; Fri, 29 Oct 1999 12:47:45 -0700 (PDT)
	(envelope-from alc@cs.rice.edu)
Received: (from alc@localhost)
	by cs.rice.edu (8.9.0/8.9.0) id OAA16504
	for current@freebsd.org; Fri, 29 Oct 1999 14:47:44 -0500 (CDT)
Date: Fri, 29 Oct 1999 14:47:43 -0500
From: Alan Cox <alc@cs.rice.edu>
To: current@freebsd.org
Subject: copy-on-write optimized faults
Message-ID: <19991029144743.Z16685@cs.rice.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5us
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I would appreciate it if people running -current would run a "vmstat -s"
and tell me if they see a NON-ZERO value for copy-on-write optimized
faults.  About six months ago, I implemented a simpler and more general
optimization at an earlier "fork in the road".  (In effect, I avoid
the creation of the redundant vm object that "copy-on-write
optimized faults" applies to.)

If I don't hear anything, I plan to remove the vestiges of this
"optimization" from the vm fault handler.

Alan


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