From owner-freebsd-threads@FreeBSD.ORG Tue Jul 4 13:08:40 2006 Return-Path: X-Original-To: freebsd-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 CE50116A4DF; Tue, 4 Jul 2006 13:08:40 +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 63DA343D45; Tue, 4 Jul 2006 13:08:40 +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 k64D8d2J011922; Tue, 4 Jul 2006 09:08:39 -0400 (EDT) Date: Tue, 4 Jul 2006 09:08:38 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: David Xu In-Reply-To: <200607040612.23493.davidxu@freebsd.org> Message-ID: References: <20060703101554.Q26325@fledge.watson.org> <200607032125.26156.davidxu@freebsd.org> <200607040612.23493.davidxu@freebsd.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, Robert Watson , freebsd-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: Tue, 04 Jul 2006 13:08:40 -0000 On Tue, 4 Jul 2006, David Xu wrote: > On Monday 03 July 2006 21:44, Daniel Eischen wrote: >> On Mon, 3 Jul 2006, David Xu wrote: >>> On Monday 03 July 2006 20:40, Daniel Eischen wrote: >>>> 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. >>> >>> it is mutex code and priority propagating which is already >>> supported by turnstile code, in theory, it is not depended >>> on scheduler. >> >> Sure it is. SCHED_FIFO and SCHED_RR are scheduling attributes. >> Mutex code and priority propagation have nothing to do with >> this. > > I have never said SCHED_FIFO and SCHED_RR is related to mutex, > in fact, I am confused that you always said them at same time. The question was what does libthr lack. The answer is priority inheritence & protect mutexes, and also SCHED_FIFO, SCHED_RR, and (in the future) SCHED_SPORADIC scheduling. That is what I stated earlier in this thread. -- DE