From owner-freebsd-current@FreeBSD.ORG Thu Mar 27 11:42:12 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05A6F37B404 for ; Thu, 27 Mar 2003 11:42:11 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 18AEA43FBD for ; Thu, 27 Mar 2003 11:42:11 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 30059 invoked by uid 1000); 27 Mar 2003 19:42:11 -0000 Date: Thu, 27 Mar 2003 11:42:11 -0800 (PST) From: Nate Lawson To: arch@freebsd.org, current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-13.2 required=5.0 tests=AWL,USER_AGENT_PINE version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: 5.x locking plan X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Mar 2003 19:42:13 -0000 My curiousity has overcome my fear of the bikeshed so I'll ask the question that has been bugging me for a while. Why haven't we gone through the tree and created a lock for each spl and then converted every spl call into the appropriate mtx_lock call? At that point, we can mark large sections of the tree giant-free and then make the locking data-based (instead of code-based) one section at a time. This is the approach Solaris took. -Nate