From owner-freebsd-current@FreeBSD.ORG Sat Oct 28 09:48:53 2006 Return-Path: X-Original-To: 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 5CD9016A415; Sat, 28 Oct 2006 09:48:53 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADAC443D49; Sat, 28 Oct 2006 09:48:52 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 3370F46CD2; Sat, 28 Oct 2006 05:48:52 -0400 (EDT) Date: Sat, 28 Oct 2006 10:48:52 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Julian Elischer In-Reply-To: <45429703.8070305@elischer.org> Message-ID: <20061028104741.Q69980@fledge.watson.org> References: <917908193.20061027102647@serebryakov.spb.ru> <20061027103924.F79313@fledge.watson.org> <45426071.7020403@elischer.org> <602423478.20061028001449@serebryakov.spb.ru> <4542896D.1050001@elischer.org> <20061027231642.GJ30707@riyal.ugcs.caltech.edu> <45429703.8070305@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Paul Allen , Lev Serebryakov , current@freebsd.org Subject: Re: KSE, libpthread & libthr: almost newbie question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 09:48:53 -0000 On Fri, 27 Oct 2006, Julian Elischer wrote: > there is class of problems (e.g. some java programs) that have THOUSANDS of > threads, each representing an active aspect of some object. How do you put > an rlimit on that without either 1/ stopping the program from working or 2/ > allowing thousands of threads to exist but not screwing other users. Does the JVM actually expose thousands of threads to the OS, or does it actually do its own M:N threading internally based on its execution model? My impression is the latter, exposing threads to the OS only when it needs them to consume kernel or CPU resources. Robert N M Watson Computer Laboratory University of Cambridge