From owner-freebsd-threads@FreeBSD.ORG Mon Jul 3 12:01:18 2006 Return-Path: <owner-freebsd-threads@FreeBSD.ORG> 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 4131C16A412; Mon, 3 Jul 2006 12:01:18 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF4C843D5A; Mon, 3 Jul 2006 12:01:16 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id E6CED78C1D; Mon, 3 Jul 2006 12:01:13 +0000 (GMT) Date: Mon, 3 Jul 2006 12:01:13 +0000 From: John Birrell <jb@what-creek.com> To: Daniel Eischen <deischen@freebsd.org> Message-ID: <20060703120113.GA24614@what-creek.com> References: <20060703101554.Q26325@fledge.watson.org> <Pine.GSO.4.64.0607030744030.5823@sea.ntplx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <Pine.GSO.4.64.0607030744030.5823@sea.ntplx.net> User-Agent: Mutt/1.4.2.1i Cc: threads@freebsd.org, Robert Watson <rwatson@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 List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads> List-Post: <mailto:freebsd-threads@freebsd.org> List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, <mailto:freebsd-threads-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 03 Jul 2006 12:01:18 -0000 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? Are there any plans to get libpthread working on the other architectures? -- John Birrell