From owner-freebsd-threads@FreeBSD.ORG Sun Jul 13 06:52:48 2003 Return-Path: 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 1BB4D37B401; Sun, 13 Jul 2003 06:52:48 -0700 (PDT) Received: from dust.freshx.de (freshx.de [80.190.100.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73AF143F75; Sun, 13 Jul 2003 06:52:47 -0700 (PDT) (envelope-from kai.mosebach@freshx.de) Received: from alpha (p508B1D97.dip.t-dialin.net [80.139.29.151]) by dust.freshx.de (Postfix) with ESMTP id 371F015E2B0; Sun, 13 Jul 2003 15:52:40 +0200 (CEST) From: "Kai Mosebach" To: Date: Sun, 13 Jul 2003 15:52:50 +0200 Message-ID: <001e01c34946$0d718e30$0100000a@alpha> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal cc: freebsd-threads@freebsd.org Subject: AW: EAGAIN failure on pthread_create X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 13:52:48 -0000 > > On Sun, 13 Jul 2003, Kai Mosebach wrote: > > Hi, > > > > i started using libkse instead of linuxthreads in my sapdb port, but now > > on kernelstart i get the message : > > > > 2003-07-13 15:29:20 4826 ERR 11008 TASKING Could not create thread: > > 'Resource exeeed (curr:48)', rc = 1 > > 2003-07-13 15:29:20 4826 ERR 11908 SYSTEM FATAL: Could not start all > > user task threads > > > > saying, that the return code of pthread_create is 1, and the number of > > created threads so far is 48, max_threads_per_proc is 150. > > You probably are creating all your threads as scope system > threads. Each scope system threads consumes a KSEG (limited > by kern.threads.max_grpups_per_proc). I don't think you > really need each thread to be scope system; try making > the port use scope process[1]. If you insist that it does > need scope system threads, then raise max_groups_per_proc. Thought of this too, because max_groups_per_proc is 50 ... First want it to run as system scope threads, (they are, you are right;), Then if working nice, i try to switch. I think the threading part is the most tricky on in sapdb to port ... > > [1] To anticipate the question, "will one thread blocking > block the entire process", no, other threads will be > run. > > -- > Dan Eischen >