From owner-freebsd-threads@FreeBSD.ORG  Sun Feb 20 00:40:30 2005
Return-Path: <owner-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 C3E8316A4CE; Sun, 20 Feb 2005 00:40:30 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9637443D3F; Sun, 20 Feb 2005 00:40:30 +0000 (GMT)
	(envelope-from davidxu@freebsd.org)
Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j1K0eSN0094902;
	Sun, 20 Feb 2005 00:40:29 GMT
	(envelope-from davidxu@freebsd.org)
Message-ID: <4217DD2A.4030603@freebsd.org>
Date: Sun, 20 Feb 2005 08:43:22 +0800
From: David Xu <davidxu@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.7.2) Gecko/20041004
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Eischen <deischen@freebsd.org>
References: <Pine.GSO.4.43.0502191404330.22284-100000@sea.ntplx.net>
In-Reply-To: <Pine.GSO.4.43.0502191404330.22284-100000@sea.ntplx.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: threads@freebsd.org
Subject: Re: thread accounting in libpthread
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
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: Sun, 20 Feb 2005 00:40:30 -0000

Daniel Eischen wrote:

> ...
>
>since it will be the only thread in the queue.  If N threads
>complete (assuming they are all at the same priority) then
>the first thread pulled from the completed list will be
>run first since it will be the first thread added to the
>run queue.
>
>  
>
note that kernel adds completed thread in reversed order.