From owner-freebsd-smp Tue Dec 5 8:31:44 2000 From owner-freebsd-smp@FreeBSD.ORG Tue Dec 5 08:31:42 2000 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from crewsoft.com (ns.aenet.net [157.22.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 2D60B37B400 for ; Tue, 5 Dec 2000 08:31:42 -0800 (PST) Received: from [63.197.8.222] (HELO wireless-networks.com) by crewsoft.com (CommuniGate Pro SMTP 3.3b5) with ESMTP id 369624; Tue, 05 Dec 2000 08:33:59 -0800 Message-ID: <3A2D18A1.48C89595@wireless-networks.com> Date: Tue, 05 Dec 2000 08:32:33 -0800 From: Cedric Berger X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: smp@FreeBSD.ORG Subject: Six-Lock? (was Re: Netgraph and SMP) References: <200012050130.SAA16944@usr02.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, Thanks for the pointer. I guess I (and many people) use use the term reader/writer lock for exactly the "SIX-lock" mechanism you describes. In fact, I always thought that whether or not readers stop entering the lock when a writer request it is a matter of "lock policy". (You can even imagine any mixed policy where new readers are allowed to enter when a write is pending to improve throughoutput, but only for during a limited time to avoid writer starvation) Cedric Terry Lambert wrote: > > > How is this SIX-pack lock any different than a standard reader-writer lock? > > Actually, here is a tutorial from HP, with pictures: > > http://jazz.external.hp.com/training/sqltables/c5s17.html > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message