From owner-freebsd-threads@FreeBSD.ORG Mon Jul 3 12:08:58 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 DB47B16A416; Mon, 3 Jul 2006 12:08:58 +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 B75CE43D5E; Mon, 3 Jul 2006 12:08:57 +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 k63C8uVZ014631; Mon, 3 Jul 2006 08:08:56 -0400 (EDT) Date: Mon, 3 Jul 2006 08:08:56 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: John Birrell In-Reply-To: <20060703120113.GA24614@what-creek.com> Message-ID: References: <20060703101554.Q26325@fledge.watson.org> <20060703120113.GA24614@what-creek.com> 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, Robert Watson 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:08:59 -0000 On Mon, 3 Jul 2006, John Birrell wrote: > On Mon, Jul 03, 2006 at 07:48:43AM -0400, Daniel Eischen wrote: >> 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). > > How important are those relative to having libpthread work on other > architectures? It's not so much getting libpthread working on the other architectures (sparc64 is the only Tier 1 (is Sparc64 Tier 1 yet?) that libpthread doesn't work on). It's being able to support the POSIX standard. That was the goal years ago when we started the process of designing a new thread library. I maintain that we have to be able to support the standard, if we can't then it's a not a good design. > Are there any plans to get libpthread working on the other architectures? Someone with sparc64-fu will have to do some grunt work, but probably some can be grok'd from NetBSD (which also uses an SA approach). -- DE