From owner-freebsd-threads@FreeBSD.ORG  Wed Dec 15 19:39:23 2004
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 7846E16A4CE
	for <freebsd-threads@freebsd.org>;
	Wed, 15 Dec 2004 19:39:23 +0000 (GMT)
Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4FD9443D55
	for <freebsd-threads@freebsd.org>;
	Wed, 15 Dec 2004 19:39:23 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from elischer.org (julian.vicor-nb.com [208.206.78.97])
	by mail.vicor-nb.com (Postfix) with ESMTP
	id 35E8D7A403; Wed, 15 Dec 2004 11:39:23 -0800 (PST)
Message-ID: <41C092EA.7060100@elischer.org>
Date: Wed, 15 Dec 2004 11:39:22 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Petri Helenius <pete@he.iki.fi>
References: <41C0898E.3090005@he.iki.fi>
In-Reply-To: <41C0898E.3090005@he.iki.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-threads@freebsd.org
Subject: Re: worker thread performance question
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: Wed, 15 Dec 2004 19:39:23 -0000



Petri Helenius wrote:

>
> With libpthread is it usually optimal to have as many worker threads 
> (CPU bound stuff) as kern.threads.virtual_cpu or have, say double the 
> number so that there is always a thread in the run queue when another 
> hits a mutex or sleep? 

Are they always runnable?
theoretically you can schedule as many as you want.
any number > NCPU should keep teh system busy, but
I'm not sure I fully understand the question.

>
>
> Pete
>
> _______________________________________________
> freebsd-threads@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-threads
> To unsubscribe, send any mail to 
> "freebsd-threads-unsubscribe@freebsd.org"