From owner-freebsd-arch Thu Dec 27 12: 0:39 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 0135E37B41F; Thu, 27 Dec 2001 12:00:15 -0800 (PST) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20011227200014.EHPE6450.rwcrmhc52.attbi.com@InterJet.elischer.org>; Thu, 27 Dec 2001 20:00:14 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA88775; Thu, 27 Dec 2001 11:43:31 -0800 (PST) Date: Thu, 27 Dec 2001 11:43:29 -0800 (PST) From: Julian Elischer To: Mike Smith Cc: Alfred Perlstein , arch@freebsd.org Subject: Re: the condvar stuff. In-Reply-To: <200112271943.fBRJh0F01276@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 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 synchronisation: primatives CV/msleep/mtx/sx/lockmanager(gone?) thread schemes: (aio/kthreads/linux-thread-support/KSE) etc :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message