From owner-freebsd-current Fri Oct 29 16: 7:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from [132.197.97.45] (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id DD2A814ECC for ; Fri, 29 Oct 1999 16:07:33 -0700 (PDT) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by [132.197.97.45] (8.9.3/8.9.3) id TAA09178; Fri, 29 Oct 1999 19:07:30 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991029144743.Z16685@cs.rice.edu> Date: Fri, 29 Oct 1999 19:07:30 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: Alan Cox Subject: RE: copy-on-write optimized faults Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG vmstat -s reports these numbers on my computer: 3649151 copy-on-write faults 1 copy-on-write optimized faults On 29-Oct-99 Alan Cox wrote: > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message