From owner-freebsd-threads@FreeBSD.ORG  Mon Feb 21 02:38:49 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 76B9C16A4CE; Mon, 21 Feb 2005 02:38:49 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5D39543D55; Mon, 21 Feb 2005 02:38:49 +0000 (GMT)
	(envelope-from davidxu@t2t2.com)
Received: from t2t2.com (davidxu@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j1L2chJx036557;
	Mon, 21 Feb 2005 02:38:47 GMT
	(envelope-from davidxu@t2t2.com)
Message-ID: <42194993.4060202@t2t2.com>
Date: Mon, 21 Feb 2005 10:38:11 +0800
From: David Xu <davidxu@t2t2.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.5b) Gecko/20030723 Thunderbird/0.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Julian Elischer <julian@elischer.org>
References: <Pine.GSO.4.43.0502191404330.22284-100000@sea.ntplx.net>
	<4217DD2A.4030603@freebsd.org> <42193303.2090500@elischer.org>
In-Reply-To: <42193303.2090500@elischer.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: Daniel Eischen <deischen@freebsd.org>
cc: threads@freebsd.org
cc: David Xu <davidxu@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: Mon, 21 Feb 2005 02:38:49 -0000



Julian Elischer wrote:
> David Xu wrote:
> 
>> 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.
> 
> 
> I guess we could fix that easily with a tail pointer.

This will break binary compatible, userland can workaround it.

David Xu