From owner-freebsd-threads@FreeBSD.ORG Sat Dec 16 01:00:59 2006 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from localhost.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 74A7816A415; Sat, 16 Dec 2006 01:00:59 +0000 (UTC) (envelope-from davidxu@freebsd.org) From: David Xu To: freebsd-threads@freebsd.org, Daniel Eischen Date: Sat, 16 Dec 2006 09:00:54 +0800 User-Agent: KMail/1.8.2 References: <34cb7c840612151000s4a3e1f2dvd71a60d66cf7c4be@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612160900.54707.davidxu@freebsd.org> Cc: Peter Edwards Subject: Re: libpthread problem + possible solution X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Dec 2006 01:00:59 -0000 On Saturday 16 December 2006 04:11, Daniel Eischen wrote: > On Fri, 15 Dec 2006, Peter Edwards wrote: > > Hi, > > > > I've a problem when a process uses: > > libpthread > > detached threads > > mixed bound/unbound threads > > suspended threads (a la pthread_resume_np()) > > > > whereby some newly created suspended threads don't get scheduled. > > I think I've tracked it down, so if someone could review the > > reasoning, I'd be grateful. > > I'm away for a few days, so I'd appreciate you waiting until > early next week -- unless David Xu looks at it and gives it > the ok. I will review it. David Xu