From owner-freebsd-threads@FreeBSD.ORG  Mon Jul  3 12:36:42 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 300A316A412;
	Mon,  3 Jul 2006 12:36:42 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9141C43E32;
	Mon,  3 Jul 2006 12:36:24 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id 17BE246C61;
	Mon,  3 Jul 2006 08:36:23 -0400 (EDT)
Date: Mon, 3 Jul 2006 13:36:23 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Daniel Eischen <deischen@freebsd.org>
In-Reply-To: <Pine.GSO.4.64.0607030744030.5823@sea.ntplx.net>
Message-ID: <20060703133454.L57091@fledge.watson.org>
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; format=flowed
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
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:36:42 -0000


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?

Robert N M Watson
Computer Laboratory
University of Cambridge