From owner-freebsd-arch Sat Jan 20 19:47: 6 2001 Delivered-To: freebsd-arch@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 9C93737B402 for ; Sat, 20 Jan 2001 19:46:49 -0800 (PST) Received: (qmail 42174 invoked by uid 1142); 21 Jan 2001 03:46:48 -0000 Date: 20 Jan 2001 19:46:48 -0800 Date: Sat, 20 Jan 2001 19:46:41 -0800 From: Jason Evans To: Dag-Erling Smorgrav Cc: arch@freebsd.org Subject: Re: First vm_zone patch Message-ID: <20010120194641.Q69199@canonware.com> References: <20010120124200.O69199@canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Sun, Jan 21, 2001 at 04:33:21AM +0100 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 04:33:21AM +0100, Dag-Erling Smorgrav wrote: > Jason Evans writes: > > On Sat, Jan 20, 2001 at 08:20:58PM +0100, Dag-Erling Smorgrav wrote: > > > The next step is to replace the simple_lock with a mutex, and add a > > > top-level mutex to protect zlist. > > FYI, I'm currently testing a patch that completely removes simplelocks. > > Does that mean I should give up reworking vm_zone? No, I just wanted to let you know that I have some patches that touch the same code. My only changes are to convert the simplelocks to mutexes, so your work is still of additional value. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message