From owner-freebsd-current@FreeBSD.ORG  Fri Feb  6 15:00:47 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8B1A516A4CE
	for <current@freebsd.org>; Fri,  6 Feb 2004 15:00:47 -0800 (PST)
Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 648CC43D3F
	for <current@freebsd.org>; Fri,  6 Feb 2004 15:00:44 -0800 (PST)
	(envelope-from julian@elischer.org)
Received: from interjet.elischer.org ([24.7.73.28])
          by comcast.net (rwcrmhc12) with ESMTP
          id <2004020623004301400hkaare>; Fri, 6 Feb 2004 23:00:43 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA33198;
	Fri, 6 Feb 2004 15:00:41 -0800 (PST)
Date: Fri, 6 Feb 2004 15:00:40 -0800 (PST)
From: Julian Elischer <julian@elischer.org>
To: Daniel Eischen <eischen@vigrid.com>
In-Reply-To: <Pine.GSO.4.10.10402061626330.24638-100000@pcnet5.pcnet.com>
Message-ID: <Pine.BSF.4.21.0402061458450.24800-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Kris Kennaway <kris@obsecurity.org>
cc: Hye-Shik Chang <perky@i18n.org>
cc: current@FreeBSD.org
Subject: Re: python ports broken (sem_destroy: Resource temporarily
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2004 23:00:47 -0000



On Fri, 6 Feb 2004, Daniel Eischen wrote:
> > 
> > Why?
> 
> System scope threads each have their own KSEG/KSE pair.
> The default thread limits in the kernel are:
> 
>   kern.threads.max_threads_per_proc: 150
>   kern.threads.max_groups_per_proc: 50
> 
> By default there are 2 KSEGs for a threaded process in
> libpthread: one for scope process threads and one for
> the signal handling thread.  That leaves 48 for left for
> application use.
> 
> Those limits are arbitrary, so you can raise/lower them
> if you don't like them.  I thought you came up with those
> limits ;-)


I know all that :-)

Why do they make system scope threads?
:-)
couldn't part of a freebsd port patch be to make them process scoe
threads.. it'd be more efficient..

> 
> -- 
> Dan Eischen
> 
>