From owner-cvs-all Mon Mar 18 8:22:48 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 2AC3C37B405; Mon, 18 Mar 2002 08:22:43 -0800 (PST) Received: (from rwatson@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2IGMh461814; Mon, 18 Mar 2002 08:22:43 -0800 (PST) (envelope-from rwatson) Message-Id: <200203181622.g2IGMh461814@freefall.freebsd.org> From: Robert Watson Date: Mon, 18 Mar 2002 08:22:43 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: www/en/smp index.sgml 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 rwatson 2002/03/18 08:22:43 PST Modified files: en/smp index.sgml Log: Various task updates relating to VM locking task: - Break out lockmgr exclusive and sx/mutex tasks from one another, and leave the original (completed) movement of mutex pool initialization task as it's own thing. - Create the task for moving to purely exclusive locks in VM rather than lockmgr shared locks. This task will involve implementation, then testing to see if it actually hurts. If this is possible, it will greatly simplify the transition to new locking primitives. Assign this to green since he's expressed willingness to work on it. - Create the task for moving from lockmgr to either mutexes or exclusive sxlocks for VM. At that point, it should be possible to start pushing Giant down into VM somewhere, subject to lack of locking for a few primitives that will still require it, and for VFS/pmap interactions. Revision Changes Path 1.52 +16 -8 www/en/smp/index.sgml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message