From owner-cvs-all Fri Aug 31 7:47: 0 2001 Delivered-To: cvs-all@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id 3AB5B37B408 for ; Fri, 31 Aug 2001 07:46:54 -0700 (PDT) Received: (qmail 66500 invoked by uid 3193); 31 Aug 2001 14:46:53 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Aug 2001 14:46:53 -0000 Date: Fri, 31 Aug 2001 10:46:53 -0400 (EDT) From: Mike Silbersack X-Sender: To: John Baldwin Cc: , , Matt Dillon Subject: Re: RE: cvs commit: src/sys/kern init_sysent.c sysv_msg.c sysv_s In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Thu, 30 Aug 2001, John Baldwin wrote: > That does need some clarification. I'm working on a paper for BSDCon that > details locking for this stuff. When its done it will be in the developer's > handbook as well. When will this paper be done, roughly? > Not really. spl's didn't stay across sleep's either. The only data 4.x locks > across a sleep is via lockmgr(). You do the same now with sx locks. Mutexes > are more replacements for spl() type functionality, except that spl's only > protected against interrupts, and were more coarsely grained. AH! Ok, the rules make much more sense now. Hm, the sx locks don't seem to be on the mutex man page - can this be documented by someone familiar with their syntax? Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message