From owner-freebsd-smp Sun Jun 27 22:14: 7 1999 Delivered-To: freebsd-smp@freebsd.org Received: from pallas.veritas.com (pallas.veritas.com [204.177.156.25]) by hub.freebsd.org (Postfix) with ESMTP id 39B1814F2C for ; Sun, 27 Jun 1999 22:14:04 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Received: from megami.veritas.com (megami.veritas.com [192.203.46.101]) by pallas.veritas.com (8.9.1a/8.9.1) with SMTP id WAA16547; Sun, 27 Jun 1999 22:14:48 -0700 (PDT) Received: from sigma.veritas.com([192.203.46.125]) (2116 bytes) by megami.veritas.com via sendmail with P:esmtp/R:smart_host/T:smtp (sender: ) id for ; Sun, 27 Jun 1999 22:13:56 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #3 built 1999-Jan-25) Received: from sigma (localhost [127.0.0.1]) by sigma.veritas.com (8.9.2/8.9.1) with ESMTP id WAA48515; Sun, 27 Jun 1999 22:13:56 -0700 (PDT) (envelope-from aaron@sigma.veritas.com) Message-Id: <199906280513.WAA48515@sigma.veritas.com> From: Aaron Smith To: Daniel Eischen Cc: dillon@apollo.backplane.com, julian@whistle.com, freebsd-smp@FreeBSD.ORG Subject: Re: high-efficiency SMP locks - submission for review In-reply-to: Your message of "Sun, 27 Jun 1999 19:07:33 EDT." <199906272307.TAA21317@pcnet1.pcnet.com> Date: Sun, 27 Jun 1999 22:13:56 -0700 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 27 Jun 1999 19:07:33 EDT, Daniel Eischen writes: >> 2/ Before we rush off and implement a new set of locking primatives, >> it might be a good idea to look at the locking primatives of a few >> other OS's.. For example Linux and MACH, and if we can get hold of >> them, Solaris and maybe the exokernel. (and sprite) > >The Vahalia book (UNIX Internals - The New Frontiers) has a pretty >good synopsis of locking systems used by various OSs (see chapter >7). At least from the programmers interface, I really like the >Solaris API (kernel mutexes and condition variables) - they are >well understood and easy to use. i want to chime in and agree with this statement. i work on a commercial filesytem for (among other platforms) solaris; and i'd have to say that of the platforms i have been exposed to, solaris' kernel synch primitives are very comfortable to use. the function of an "rwlock" is immediately understood by anybody who understands reader-writer locks. mutex, condition variables, etc are all very accessible ideas. for this reason i think it's counterproductive to use opaque names such as "qlock". it's the same reason i have an issue with "lockmgr". i'm happy to see activity in this area! aaron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message