From owner-freebsd-smp Thu Jul 17 13:30:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA02654 for smp-outgoing; Thu, 17 Jul 1997 13:30:20 -0700 (PDT) Received: from critter.dk.tfs.com (critter.phk.freebsd.dk [195.8.133.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA02637; Thu, 17 Jul 1997 13:30:09 -0700 (PDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id WAA18582; Thu, 17 Jul 1997 22:27:40 +0200 (CEST) To: Steve Passe cc: smp@freebsd.org, Peter Wemm , dyson@freebsd.org From: Poul-Henning Kamp Subject: Re: pushdown of "giant lock" In-reply-to: Your message of "Wed, 16 Jul 1997 14:25:34 MDT." <199707162025.OAA09649@Ilsa.StevesCafe.com> Date: Thu, 17 Jul 1997 22:27:40 +0200 Message-ID: <18580.869171260@critter.dk.tfs.com> Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707162025.OAA09649@Ilsa.StevesCafe.com>, Steve Passe writes: >Hi, > >DESIGN PROPOSAL: > >The following documents a 1st draft proposal for achieving finer-grained >locking. Please comment, paying particular attention to the pseudo-code >I propose for doing it. As the guy who's done it before and in this case did it last time, let me add some other input to this topic: 1. Add a optional (possibly compile-option) circular buffer which will record the lock actions. 2. Add a permanent version of the ugly serial-port stuff, under a compile- time option of course, to record the lock actions. 3. Consider redesigning the lock implementation for the purpose, rather that try to modify the rather special lock we have now... Just my .25 DKR. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail.