From owner-cvs-all Mon Mar 18 7:16:43 2002 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6ECEA37B6DF; Mon, 18 Mar 2002 07:08:59 -0800 (PST) Received: (from green@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2IF8Am41245; Mon, 18 Mar 2002 07:08:10 -0800 (PST) (envelope-from green) Message-Id: <200203181508.g2IF8Am41245@freefall.freebsd.org> From: Brian Feldman Date: Mon, 18 Mar 2002 07:08:10 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/vm vm_fault.c vm_glue.c vm_map.c vm_map.h vm_pageout.c vm_zone.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG green 2002/03/18 07:08:10 PST Modified files: sys/vm vm_fault.c vm_glue.c vm_map.c vm_map.h vm_pageout.c vm_zone.c Log: Back out the modification of vm_map locks from lockmgr to sx locks. The best path forward now is likely to change the lockmgr locks to simple sleep mutexes, then see if any extra contention it generates is greater than removed overhead of managing local locking state information, cost of extra calls into lockmgr, etc. Additionally, making the vm_map lock a mutex and respecting it properly will put us much closer to not needing Giant magic in vm. Revision Changes Path 1.132 +10 -16 src/sys/vm/vm_fault.c 1.131 +3 -1 src/sys/vm/vm_glue.c 1.217 +58 -60 src/sys/vm/vm_map.c 1.72 +10 -20 src/sys/vm/vm_map.h 1.192 +2 -1 src/sys/vm/vm_pageout.c 1.54 +6 -6 src/sys/vm/vm_zone.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message