From owner-freebsd-arch@FreeBSD.ORG Fri Mar 28 20:46:31 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B07D937B401; Fri, 28 Mar 2003 20:46:31 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC94443F3F; Fri, 28 Mar 2003 20:46:30 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0191.cvx21-bradley.dialup.earthlink.net ([209.179.192.191] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18z8ET-0003HI-00; Fri, 28 Mar 2003 20:46:18 -0800 Message-ID: <3E8524C0.5F80D3D@mindspring.com> Date: Fri, 28 Mar 2003 20:44:48 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" References: <20030327143259.I64602-100000@mail.chesapeake.net> <3E843009.2060104@tcoip.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4d6b804bc6589c5b91231a495bc3d307ba2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c cc: arch@freebsd.org cc: Scott Long Subject: Re: 1:1 threading. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2003 04:46:33 -0000 "Daniel C. Sobral" wrote: > David Xu wrote: > > do you think that a multithreaded process should use more CPU time then > > a single thread process, so threaded process should have higher priority > > and block other single thread processes out? AFAIK, threading is not > > designed for this, you may misunderstand what threading is designed for. > > Threading might not have been originally designed for this, but a lot of > people use it this way, a lot of people *want* it this way, and POSIX > specifically mandates that this way be available. > > So let's drop that issue, please. A side question... Is there an administrative limit on the number of threads that you can create in a process, such that the total number is limited to the number of processes you are administratively limited to creating? I.e., the administrative limit on number of child processes is implicitly an administrative limit on how much quantum you can use; is the limit still enforced on threads, as well? -- Terry