From owner-freebsd-threads@FreeBSD.ORG Mon Jul 3 12:41:12 2006 Return-Path: X-Original-To: threads@freebsd.org Delivered-To: freebsd-threads@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00D7816A407; Mon, 3 Jul 2006 12:41:12 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 363F643E6D; Mon, 3 Jul 2006 12:40:37 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k63Cebj9014470; Mon, 3 Jul 2006 08:40:37 -0400 (EDT) Date: Mon, 3 Jul 2006 08:40:37 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Robert Watson In-Reply-To: <20060703133454.L57091@fledge.watson.org> Message-ID: References: <20060703101554.Q26325@fledge.watson.org> <20060703133454.L57091@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: threads@freebsd.org Subject: Re: Strawman proposal: making libthr default thread implementation? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jul 2006 12:41:12 -0000 On Mon, 3 Jul 2006, Robert Watson wrote: > > On Mon, 3 Jul 2006, Daniel Eischen wrote: > >>> - Are there technical features present in libpthread that aren't yet in >>> libthr, and are required? In the past system/local thread support has >>> been >>> the complaint, but I believe that is now long fixed. This is useful >>> regardless of a switch. >> >> Yes, you have to support PTHREAD_PRIO_PROTECT, PTHREAD_PRIO_INHERIT >> mutexes, and SCHED_RR, SCHED_FIFO, and SCHED_SPORADIC scheduling (hopefully >> not under the restriction that you are a privileged user). >> >> If you can those in libthr, I have no objection. However, these are not as >> easy to do in 1:1. > > Thanks for leeting me know. Other than thee above missing scheduling > functionality, are you aware of any other missing or substantially > non-functional features in libthr that are important to this discussion? No, I think those are what libthr lacks in supporting POSIX. I think the problem will be getting our 3 kernel schedulers to support them. -- DE