From owner-freebsd-current Tue Aug 25 00:55:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16776 for freebsd-current-outgoing; Tue, 25 Aug 1998 00:55:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16770 for ; Tue, 25 Aug 1998 00:55:33 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA00249 for current@freebsd.org; Tue, 25 Aug 1998 02:34:25 -0500 (EST) (envelope-from toor) Message-Id: <199808250734.CAA00249@dyson.iquest.net> Subject: Follow-up on the busy page problem To: current@FreeBSD.ORG Date: Tue, 25 Aug 1998 02:34:25 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It appears that the usage of PG_BUSY and m->busy is distorted. m->busy is used for the buffer cache code to show that I/O is active on a page. PG_BUSY blocks all other concurrent activity, while m->busy allows other concurrent activity. PAGE_BUSY would be used to set the PG_BUSY bit, while one would incr m->busy when doing concurrent (or sequential) I/Os. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message