From owner-freebsd-fs Wed Sep 20 0: 4:39 2000 Delivered-To: freebsd-fs@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id 4400437B422 for ; Wed, 20 Sep 2000 00:04:37 -0700 (PDT) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id JAA32523; Wed, 20 Sep 2000 09:04:32 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id JAA30216; Wed, 20 Sep 2000 09:04:32 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 20 Sep 2000 09:04:32 +0200 (CEST) From: Marius Bendiksen To: Terry Lambert Cc: Christopher Stein , freebsd-fs@FreeBSD.ORG Subject: Re: how mmap buffer writes handled? In-Reply-To: <200009190615.XAA13756@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > use some of the protection facilities or such to force an exception to be > > raised when accessing the page for write, and updating the statistics > > based on that. > as being dirty. If you look at the VM code, you will see that > the page is actually mapped elsewhere, and the page not present > fault is trapped, and then looked up in a translation table, 8-p. Indeed, so it does. But why would we have code to handle this on i386? Marius (PS: The method you mentioned would still qualify as "force an exception to be raised when accessing the page for write" ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message