From owner-freebsd-arch Thu Dec 27 12:14:21 2001 Delivered-To: freebsd-arch@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 2A0A537B405; Thu, 27 Dec 2001 12:14:13 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id C252481E0C; Thu, 27 Dec 2001 14:14:12 -0600 (CST) Date: Thu, 27 Dec 2001 14:14:12 -0600 From: Alfred Perlstein To: Julian Elischer Cc: Mike Smith , arch@freebsd.org Subject: Re: the condvar stuff. Message-ID: <20011227141412.G55891@elvis.mu.org> References: <200112271943.fBRJh0F01276@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Thu, Dec 27, 2001 at 11:43:29AM -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Julian Elischer [011227 14:00] wrote: > so, is there such a thing in > pthread condvars as an uncancellable condvar? > > > On Thu, 27 Dec 2001, Mike Smith wrote: > > No, they are condition variables. > > > > They exist to provide a mechanism that is familiar to a large number of > > thread programmers, and which has a good body of related algorithms > > already established. > > > > They directly parallel the condition variables found in the pthread > > library, again keeping the kernel and userland programming metaphors as > > close as is practical. > > I don't know how good an idea this is.. > we are getting VERY kitchen-sinky in the kernel. Can I have a C++ > allocator too? > > enumerate: > mem allocators: mbuf/malloc/zalloc/kvalloc-etal/bus-space-alloc I hope to finish my slab allocator in the next couple of months this should collapse malloc and zalloc into a single subsystem. > synchronisation: primatives CV/msleep/mtx/sx/lockmanager(gone?) Eventually we will be able to get rid of msleep. > thread schemes: (aio/kthreads/linux-thread-support/KSE) > etc :-) Hopefully KSE will be flexible enough to implement aio, kthreads and linux-threads with a small wrapper, right? :) -- -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.' Tax deductable donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message