From owner-freebsd-arch Sat Jan 20 11:21:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id A9D1737B400 for ; Sat, 20 Jan 2001 11:21:00 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id UAA61600; Sat, 20 Jan 2001 20:20:59 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: arch@freebsd.org Subject: First vm_zone patch From: Dag-Erling Smorgrav Date: 20 Jan 2001 20:20:58 +0100 Message-ID: Lines: 14 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://people.freebsd.org/~des/software/vm_zone-20010120.diff Currently, zalloci() and zfreei() always lock the zone, while zalloc() and zfree() only do so in SMP kernels. This patch removes zalloci() and zfreei() and makes zalloc() and zfree() always lock the zone. It also cleans up vm_zone.[ch] a little. I've verified that a patched kernel builds, but not that it runs. The next step is to replace the simple_lock with a mutex, and add a top-level mutex to protect zlist. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message