From owner-cvs-all Fri Aug 31 0:15:36 2001 Delivered-To: cvs-all@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id D7EBA37B405; Fri, 31 Aug 2001 00:15:29 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id A455681D01; Fri, 31 Aug 2001 02:12:47 -0500 (CDT) Date: Fri, 31 Aug 2001 02:12:47 -0500 From: Alfred Perlstein To: John Baldwin Cc: Mike Silbersack , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, Matt Dillon Subject: Re: cvs commit: src/sys/kern init_sysent.c sysv_msg.c sysv_s Message-ID: <20010831021247.M81307@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Aug 30, 2001 at 11:57:43PM -0700 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 * John Baldwin [010831 02:00] wrote: > > 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. You're aware of this, but just to clarify, you were also implicitly protected from non-interrupt threads by the mutual exclusion, however this is no longer the case, multiple threads may be in the kernel at the same time, and you better be prepared for your footing to disappear out from under you unless you use some sort of lock. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message